Review Checklist Design
Design effective review checklists that surface defects without slowing teams down. Use when creating domain-specific review criteria.
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 review-checklist-designgit clone --depth 1 https://github.com/sethdford/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/tech-lead/code-review-leadership/skills/review-checklist-design ~/.claude/skills/review-checklist-designPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Review Checklist Design Create checklists that guide reviewers without creating busywork. ## Context You are helping design review checklists for specific domains (backend services, frontend components, infrastructure, security). If you have code samples or known defect patterns, use them. ## Domain Context - Toyota's andon cord system: checklists should surface problems _before_ they reach customers - Cognitive science research: humans are poor at remembering checklists; automation is better than willpower - High-performing teams (Forsgren et al., "Accelerate"): checklists enable distributed review without bottlenecks Key principles: 1. **Automate what you can**: Linters, formatters, and CI gates handle style. Checklists should focus on judgment calls 2. **Domain-specific matters**: A backend service checklist differs from a frontend component checklist. Customize, don't reuse 3. **Checklists are teaching tools**: Each item should teach reviewers what to look for ## Instructions 1. **Identify defect categories**: Ask engineers "what defects did we miss in review?" Group by type (performance, security, logic, maintainability) 2. **For each category, write one checklist item**: Example: "Performance: does this query use indexes, or could it N+1?" not "Are queries efficient?" 3. **Add failure examples**: Each checklist item should have a 1-2 line example of what to catch 4. **Separate automation from judgment**:
Details
- Skill name
review-checklist-design- Repository
- sethdford/claude-skills
- Path
tech-lead/code-review-leadership/skills/review-checklist-design/SKILL.md- License
- MIT
- Repo updated
- 11 March 2026
FAQ
What does the Review Checklist Design skill do?
Design effective review checklists that surface defects without slowing teams down. Use when creating domain-specific review criteria.
How do I install the Review Checklist Design 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 Review Checklist Design 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.
Risk Assessment
48sethdford/claude-skills
Identify and manage architectural risks using risk matrices and mitigation strategies.
Responsive Design
48sethdford/claude-skills
Design adaptive layouts and interactions that work across all screen sizes and input methods.
Roadmap Design
48sethdford/claude-skills
Structure a credible, transparent roadmap that communicates strategy and commitment.
Browse the most popular Claude skills, all other skills, or write your own with the skills generator.