← All skills
✅
Engineering
Code Review Checklist
What to actually check in a code review. Logic, tests, naming, security, performance, docs.
Step 1
Get the skill
Pick one. Copy to paste straight away, or download code-review-checklist.md to keep.
Step 2
Paste it into your AI
Avoid the "looks good to me" review. 5 specific comments build the engineer; 0 builds nothing.
▸Preview the skill· what gets copied
Run a code review.
Code / diff to review: {{PASTE PR DIFF or LINK}}
Language / framework: {{STACK}}
Repo conventions: {{NOTES}}
Check in this order:
1. Does it do what the PR description says
2. Logic correctness (bugs, off-by-one, race conditions)
3. Test coverage (added, meaningful, not just snapshots)
4. Edge cases (null, empty, large, concurrent)
5. Security (input validation, secrets, auth)
6. Performance (N+1, unbounded loops, large memory)
7. Naming + readability (would a junior follow this?)
8. Comments (only on WHY, never WHAT)
9. Dead code or commented-out blocks
10. Docs / changelog updates
11. Migration / rollback safety
12. Backwards compatibility
Output: numbered comments. Mark each as Blocking / Suggestion / Nitpick.Works with: Claude · Claude Code · ChatGPT · Cursor · Any model
By Rishi Jain
More skills like this
⌨️
Claude Code Project Spec
Hand Claude Code a project spec it can actually build from. Stack, files, behavior, edge cases.
🐛Bug Report Polisher
Turn "this is broken plz fix" into an actionable bug report. Repro, expected, actual, env, logs.
🔁Self-Eval Prompt Wrapper
Forces the AI to grade its own output and rewrite if it scores below 8 of 10. Quality control built in.