AI pull request reviews with code graph context

Reviews brings pull requests, findings, and code-graph context together in Graphify. Use it to understand a change and the code it can affect.

​

When a review runs

Graphify reviews a pull request when it is opened, reopened, or marked ready for review. A draft is skipped until it is marked ready. A later push to the pull request does not start another review. To review the current head after new commits, a repository owner, member, or collaborator comments @graphify review on the pull request. The review uses the indexed default-branch graph plus that pull request’s diff. It does not index the head branch. Repositories and builds explains which branch the graph follows.

​

Turn reviews off

On Repositories, open Options for the repository and switch PR reviews off. Automatic reviews stop, and @graphify review does not start one. Indexing stays on. Formal verification stays on until its own switch is turned off.

​

Review a change

1. Open Reviews and choose the repository.
2. Select the relevant pull request and review run. Check the commit so you know which revision was analyzed.
3. Inspect the findings, source context, and affected code. Follow the pull request or commit link to investigate further.
4. Compare advisory findings with the run’s verification evidence, where present.

Graph context helps you look beyond the diff: callers, dependencies, and relationships can explain why a small edit has wider effects.

​

Review and verification

Advisory review findings and formal verification results answer different questions. A review can surface a concern to investigate. Verification compares supported changed functions. Read each label in Formal verification: proved equivalent, a behavior change, no divergence sampled, an abstention, or an error. Use the Formal Verification view for the run history and per-function verdicts. Do not interpret a completed review as proof that all changed functions preserve behavior.

​

Improve future reviews

Give feedback on the pull request with @graphify wrong <finding>, @graphify good <finding>, or @graphify suppress <rule>. Use exact finding names from the review. The Learn view shows learned dismissals, suppressed patterns, and feedback history. This adjusts advisory surfacing without changing verification verdicts.

​

Repository review settings

On Repositories, open Options for a repository. PR reviews turns the review bot on or off, as described above. These two switches are on unless you turn them off. Neither blocks a merge.

• Risky patterns lists risky patterns on lines the pull request adds. The review can then include Risky patterns (advisory).
• Stale docs lists docs that mention code the pull request changed. The review can then include Docs that may be stale (advisory).

Expand the repository row to see Unreferenced code (heuristic). It is not a switch. The card appears when indexing is on and the graph has nodes. It lists private functions, methods, and classes that nothing in that repository’s graph references, and that a text search of the source finds no other use of. A symbol is listed only after it has stayed unreferenced for the number of days the card states, across at least two indexed builds. Code reached through reflection, a string lookup, or another repository can still appear, so check it before you remove it.

​

Missing or outdated results

Check the selected repository and commit, the settings above, and any plan-limit or access message. A result for an older commit describes that earlier revision. Repositories and builds explains where to check indexing and repository controls.

​

Next steps