Home › Prompts › Claude › Thorough pull request review
Thorough pull request review
A structured code review focused on correctness, security and maintainability, with severity labels and concrete fixes.
ClaudeCodingRuleStack original
Written for Claude Opus 5.5 · Updated 2026-10-16
Note: Review and test before use. Provided as is, without warranty. See Terms.
Prompt
DownloadReview this pull request. Context: [what it should do, link to issue]. Language/framework: [stack].
<diff>
[paste diff]
</diff>
Report in this order: 1) Bugs and correctness issues, 2) Security issues, 3) Missing tests, 4) Maintainability. For each finding give severity (blocker/major/minor/nit), the file and line, why it matters, and a concrete fix (code if short). Don't comment on style that a linter would catch. End with a verdict: approve, approve with changes, or request changes.Replace everything in [square brackets] with your own details.
Settings & parameters
claude-opus-5-5with highereffortfor large diffs; 1M-token context fits big PRs
Variations
- Security-only review with OWASP categories.
- Review against your team's AGENTS.md conventions (paste them in <conventions>).
Tips
- Include the issue/spec; reviews without intent catch less.