🔎Coding
Review a Pull Request for Real Risks
A code-review prompt that prioritizes correctness, security, regressions, and missing tests over cosmetic comments.
Best for: Engineering teams
Prompt template
Review this pull request as a senior maintainer. CHANGE INTENT [Describe what the PR is supposed to accomplish.] REPOSITORY CONSTRAINTS [List architecture rules, compatibility requirements, and security boundaries.] DIFF / FILES [Attach or point to the changed files.] REVIEW PRIORITIES 1. Correctness defects and broken edge cases. 2. Security, authorization, privacy, or data-integrity risks. 3. Backward-compatibility and migration problems. 4. Concurrency, error handling, and partial-failure behavior. 5. Missing tests that would catch a realistic regression. Ignore formatting or naming preferences unless they create a concrete maintenance risk. For every finding, cite the exact file and smallest useful line range, describe the failure scenario, and propose a bounded correction. Do not invent issues merely to fill a list. Finish with: - Merge recommendation: approve / request changes - Highest-risk unresolved item - Tests that should run before merge
Customize before using
- Add repository-specific invariants.
- Provide the PR intent separately from the implementation.
- Ask for only actionable findings.
Result quality checks
- Every finding has a concrete failure scenario.
- Comments point to precise code locations.
- Review does not confuse preference with defect.