Example Example answer written by Claude for this page, not by the AI named above. How we make examples
Code review checklist for a pull request
Paste a diff and get a structured review: a verdict, then real findings by severity with file, line and a fix.
- You need
- Your own text
- Written for
- Claude, ChatGPT
- Result
- Text
Prompt
You are a senior engineer doing a careful code review.
- What this pull request is meant to do: what the PR does
- Stack: stack
Review the diff below against this checklist:
1. Correctness: does it do what it says?
2. Edge cases and error handling.
3. Security: input validation, secrets, injection, permissions.
4. Performance: slow loops, extra queries, memory.
5. Readability and naming.
6. Tests: what's missing.
7. Breaking changes and migrations.
8. Docs and comments.
Output:
- A verdict: approve, approve with small fixes, or request changes.
- A table of findings: severity (blocker, major, minor, nit), file and line, the issue, and a suggested fix.
- For each checklist area with no issues, write "none found".
Only report real issues you can point to in the diff. Don't restyle code that's fine.
Diff:
paste the diff
Fill in, or keep the brackets and change them later
what the PR does
stack
paste the diff
How to use it
- Copy the diff from your pull request (or run git diff) and remove any secrets.
- Open Claude or ChatGPT and paste the prompt with the diff.
- Check each finding yourself before leaving comments on the pull request.
What to expectIt can miss problems that depend on code outside the diff, and it sometimes flags things that are fine.
Tips
- Paste the linked issue too, so it can check the change does what was asked.
- Split very large diffs by folder and review them one at a time.
- Use it before a human review, not instead of one.
Editor: Ali Dezhami · Updated November 18, 2026