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

​
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 Cloud 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 and reports proof, a behavior change, empirical agreement, or an abstention. 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.

​
Missing or outdated results

Check the selected repository and commit, repository review settings, 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.