How to Review Pull Requests With Claude Opus 4.6
Claude Opus 4.6 can review a pull request diff and flag likely bugs, missing edge cases and inconsistent patterns before a human reads it. It works best on diffs of a few hundred lines with the surrounding files supplied as context.
An AI reviewer does not replace a teammate. It catches the mechanical problems so a human can spend attention on design and intent, which is where review time is actually worth spending.
What should you feed the model?
The diff plus the files it touches, not the whole repository. Whole-repo context wastes tokens and buries the change.
- Paste the unified diff under a clear heading.
- Include the full content of files the diff modifies, at least the functions involved.
- Add the test files, if any, so it can see whether coverage exists.
- State the project’s conventions in a short line or two.
How do you structure the review prompt?
Ask for categories, ranked by severity. A flat list of comments is unusable because the reader cannot tell a crash from a nitpick.
Something like: “Review this diff for (1) correctness bugs, (2) security issues, (3) missing edge cases, (4) style inconsistencies. Rank each as high, medium or low. Quote the line. Do not comment on formatting.”
That last clause matters. Without it you get a wall of whitespace and naming complaints that drown out the real finding.
What does it actually catch well?
| Category | Reliability |
|---|---|
| Null / undefined handling | High |
| Off-by-one and boundary bugs | High |
| Missing error handling | High |
| Injection / auth gaps | Medium |
| Architecture / design | Low |
It is strong on the mechanical layer and weak on judgment calls that depend on the team’s roadmap. Do not expect it to tell you whether the feature should exist.
How do you cut the false-positive noise?
Two habits help. First, tell it what the diff intends — “this adds retry logic to the payment call” — so it does not flag intentional behavior as a bug. Second, ask it to state its confidence per finding and to omit anything below medium.
Even then, expect some noise on unfamiliar frameworks. Treat the output as a checklist, not a verdict.
What does this cost?
Opus 4.6 sits at the premium end of API pricing, and a diff plus context can be tens of thousands of tokens. Reviewing every small commit with it is wasteful. Reserve it for substantial changes — the ones where a missed bug would reach production.
A lighter model can handle trivial diffs; escalate to Opus 4.6 when the change touches payment, auth or data deletion.
Key Takeaways
- Feed the diff plus the full modified files, not the whole repository.
- Ask for severity-ranked categories and forbid formatting commentary.
- Strongest on null handling, boundaries and missing error paths; weak on architecture.
- Premium pricing means reserving it for substantial or risky changes.
Last updated: September 2026.
