Skip to main content
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. After a push, the new commit has no Graphify check run until someone asks for a review. After new commits, a repository owner, member, or collaborator comments @graphify review on the pull request. Each review analyzes the full pull request, from where it branched to its latest commit. Reviews use the graph to understand how the changes affect the surrounding code. Reviews compare the pull request’s changes against the indexed default branch. Nothing from the pull request’s branch is saved as an index. Repositories and builds explains which branch the graph follows.

Cross-repo impact

When a repository is part of a cross-repository graph, its pull request reviews also load the latest graphs of the other repositories in that graph. Graphify links those repositories through the types they share and the calls between them. The review comment then includes a Cross-repo impact section. It says “This change impacts N symbol(s) across M peer repo(s)” and lists each affected repository with up to 10 of its symbols. It covers callers and dependents in the other repositories. If nothing is affected, the section says no cross-repo impact was detected among the indexed peer repositories. It also warns you when some repositories in the group aren’t indexed yet. The section is advisory. It never changes whether the Graphify check passes or fails. There’s nothing to turn on. To set it up, open Graphs > Cross-Repository in the app and select Combine repositories. A combined graph needs at least two repositories. See Combine repositories.

Know when a review is ready

A review shows up in two places on the pull request: a review comment from the Graphify app, and a check run named Graphify on the reviewed commit. Formal verification posts its own check run, Graphify Formal Verification, and runs on every push. Graphify doesn’t push a message to your coding agent when a review lands. Your agent can ask for the result with the hosted MCP review_status tool: pass a PR number for one review, or omit it to get the 10 most recent. See what review_status returns. To wait on GitHub itself, point the agent at the Graphify check run and the review comments:

Review again after a fix

When you push fixes and comment @graphify review, Graphify analyzes the full pull request, from where it branched to its latest commit. The new review doesn’t list which earlier findings were fixed, and it doesn’t carry them over. Check each earlier finding against your fix. If a finding is wrong or no longer applies, tell Graphify with @graphify wrong <finding> so it learns from it. See Improve future reviews.

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.
Graphify Reviews with pull request runs, findings, and affected code 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. Each function gets one of the labels in Formal verification: Behavior changed, Proven same, No change found, Not checked, or Couldn’t run. 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.

Limits, skips, and the review queue

When Graphify cannot start a review because of a plan limit, the skip is visible on the pull request’s Graphify check (and as a notice on Reviews when the workspace is over its review allowance). Examples:
  • Monthly or daily review limit reached: the check says reviews resume at the next UTC reset, and links to billing.
  • Usage limit reached: same idea for the workspace usage cap.
When the workspace already has its maximum number of reviews running, a new review waits in line instead of being dropped. The check shows Queued with how many reviews are already running. If it does not start within the queue age limit, it is dropped; comment @graphify review to retry. Concurrent review limits by plan are on Plans and pricing.

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

Connect your agent

Add the hosted MCP at api.graphify.com/mcp. Sign in with OAuth, no API key.

Read a review and a verdict

What each finding means.

Formal verification

How verdicts are checked.