Code Review Checklist
Systematic code review process, feedback templates, approval criteria, and review best practices.
Install
/plugin marketplace add sethdford/claude-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add sethdford/claude-skills --skill code-review-checklistgit clone --depth 1 https://github.com/sethdford/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/engineer/engineer-toolkit/skills/code-review-checklist ~/.claude/skills/code-review-checklistPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Code Review Checklist
Conducting effective code reviews that improve quality and share knowledge.
## Context
You are reviewing code. Be thorough but kind; goal is learning and quality.
## Domain Context
- **Correctness**: Does code do what it claims?
- **Testing**: Are there tests? Do they cover important cases?
- **Readability**: Can a new person understand it?
- **Performance**: Is it efficient? Any obvious issues?
- **Security**: Are there security risks?
- **Style**: Does it follow team conventions?
## Instructions
1. **Correctness**: Does this solve the problem? Are edge cases handled?
2. **Tests**: Are tests comprehensive? Do they test behavior, not implementation?
3. **Code Quality**: Naming clear? Functions small? DRY?
4. **Performance**: Any N+1 queries? Unnecessary copying?
5. **Security**: No secrets? No SQL injection? Safe input handling?
6. **Comments**: Only if explaining _why_, not _what_
7. **Approval**: Is this good enough to merge?
## Anti-Patterns
- Blocking on style; use linters instead
- Nitpicking without understanding context
- Vague feedback ("improve this"); be specific
- Ignoring tests; they're critical
- Approving without reading code
- Personal criticism ("you always do this"); focus on code
## Further Reading
- Google Code Review Guidelines
- The Art of Code Review (Sarah Drasner)Details
- Skill name
code-review-checklist- Repository
- sethdford/claude-skills
- Path
engineer/engineer-toolkit/skills/code-review-checklist/SKILL.md- License
- MIT
- Repo updated
- 11 March 2026
FAQ
What does the Code Review Checklist skill do?
Systematic code review process, feedback templates, approval criteria, and review best practices.
How do I install the Code Review Checklist skill?
Claude Code plugin: /plugin marketplace add sethdford/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Code Review Checklist popular?
It lives in sethdford/claude-skills, which has 48 GitHub stars and 10 forks.
Related skills
A B Test Design
48sethdford/claude-skills
Design rigorous A/B tests with hypotheses, variants, metrics, and sample size calculations.
A B Test Design Pm
48sethdford/claude-skills
Analytics and experimentation skill for product managers.
Abuse Case Design
48sethdford/claude-skills
Design abuse cases (negative use cases) showing how attackers misuse system features. Use when identifying attacks that exploit intended functionality or business logic flaws.
Git Workflow
48sethdford/claude-skills
Feature branches, commit hygiene, rebasing vs. merging, and collaborative workflows.
CI CD Pipeline Design
48sethdford/claude-skills
GitHub Actions, GitLab CI, Jenkins; stages, artifacts, caching, and deployment automation.
Review Metrics
48sethdford/claude-skills
Track code review health metrics (cycle time, review participation, defect escape) to improve review process. Use when analyzing review effectiveness.
Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.