Topic · Pull request review

What is a pull request review, and how do I keep the requirement side true in CI?

Gist

A pull request review is usually comments on the diff. Proof prints the requirement blast radius on this branch with proof review-pr, so a reviewer does not reconstruct it from raw YAML.

proof review-pr --format comment

Keep GitHub if you need the thread. Keep CodeRabbit if you want comments on the Go. Proof does not replace that UI, and LGTM on the diff is not the requirement graph.

Request demo Last LGTM vs this brief

01 · The diff is not the neighborhood

Approving the Go is not reviewing the shall that moved.

A reviewer reads the patch. The requirement file may have changed two hops away. The approval stamp may now be stale. The git diff does not say that.

The AI-review compare lives on Proof vs CodeRabbit. The merge gate on a requirement lives on gating AI pull requests on a requirement. The blast-radius walk after a shall moves lives on software change impact analysis. This page is the brief on the branch: which requirements changed, which fields, whether they need re-approval, and which files to inspect first.

The command is deterministic. It does not call a model. It does not approve the pull request. It complements the diff.

proof review-pr --format comment
proof review-pr --base main
proof review req SYS-REQ-010

The first command posts a comment-shaped brief. The second pins the merge base. The third is one requirement's neighborhood after you have the list. Printing LGTM after the brief is how the shall drifted.

02 · The exhibit

Same pull request. A comment thread, or this brief.

The diff still has the Go. SYS-REQ-010 changed two files away. Click the tabs.

GitHub / CodeRabbit

Opened pkg/numeric/limit.go
Comment LGTM on the function

Diff reviewed

This branch

SYS-REQ-010 description changed. Approval is stale. The thread did not say that.

No requirement list

GitHub / CodeRabbit

Still the Go comment. Still a thumbs-up.

Keep the thread

Proof

Ask which shalls moved on this branch
Out SYS-REQ-010 needs re-approval; inspect limit.go + the child

Brief is not an approve

Same pull request. A comment thread, or this brief. Click the tabs.

What the brief lists	What Proof actually does	What a green cell is not
Changed requirements	Requirement files and authored fields that moved on the branch	Not a semantic read of the Go. Keep GitHub.
Approval drift	Whether a changed shall now needs approval or re-approval	Not the GitHub Approve button.
Blast radius	Files and linked requirements to inspect first	Not MC/DC on the function. Keep MC/DC for Go.
No requirement files changed	Still not a free pass. Owned production code can move without a YAML edit	Not “nothing to review.” Check `proof workflow check --stage implement --only authored_delta_expected`.
AI comment	Optional Visor job reads this brief later. This command stays deterministic	Not CodeRabbit. Not Copilot. Not this CLI calling a model.

Formats for the brief itself:

proof review-pr --format plain
proof review-pr --format comment
proof pr-review --base main

Plain is for a terminal. Comment is for the thread. The alias proof pr-review is the same command. If a requirement was deleted, the brief still wants retirement or supersession named. It does not retire the shall for you.

We have not run GitHub review, CodeRabbit, and Proof on the same frozen pull request, and we have not scored this brief as a proof of the Go. The loss is named, not scored.

03 · The honest loss

A green Proof brief is not a pull request review.

The command compresses requirement context. Proof will not pretend that stdout is an approve.

GitHub still owns the thread, the required reviewers, and the merge button. CodeRabbit still comments on the diff. SonarQube still gates quality. Proof lists which shalls moved and where to look next. It does not independently prove those shalls are the right shalls. It does not execute the tests. Keep the review.

Proof is not GitHub. It is not Copilot. It is not a semantic reader of the patch. Jama still authors the shall. VectorCAST or LDRA still win at a qualified C toolchain.

The AI-review compare still lives on Proof vs CodeRabbit. The merge gate still lives on gating AI pull requests on a requirement. The impact walk still lives on software change impact analysis.

Request demo How the install is bought

04 · Nearby questions

What people type next.

How do I review a pull request? GitHub's own docs still win that how-to. This page is the requirement-side brief on the same branch. proof review-pr --format comment.

Is Proof an alternative to GitHub pull request review? No. Keep the thread. Proof prints which shalls moved. Jama still authors.

Is Proof an alternative to CodeRabbit? No. CodeRabbit comments on the Go. The compare lives on Proof vs CodeRabbit.

What if no requirement files changed? The brief can still be short. Owned code can move without a YAML edit. Record that with proof review impact SYS-REQ-010 --decision no-authored-change --reason "…" after you have looked.

What is software change impact analysis? The walk from one shall to its neighbors. That H1 lives on software change impact analysis as proof trace impact SYS-REQ-096 --format table.

How do I gate an AI pull request on a requirement? That H1 lives on gating AI pull requests on a requirement.