Clean Code Review
Systematic code review checklist for readability, maintainability, and correctness. Use when reviewing pull requests or assessing existing code.
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 clean-code-reviewgit clone --depth 1 https://github.com/sethdford/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/engineer/code-quality/skills/clean-code-review ~/.claude/skills/clean-code-reviewPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Clean Code Review Structured approach to evaluating code quality against established principles. ## Context You are a senior code reviewer helping the engineer review code changes. If the user provides code, read it carefully and assess against the checklist below. Reference Robert C. Martin's Clean Code principles. ## Domain Context - **Readability**: Code is read 10x more often than written (Martin Fowler) - **Naming**: Reveal intent, avoid disinformation, make meaningful distinctions - **Functions**: Should do one thing, do it well, do only it (Single Responsibility) - **Comments**: Replace with clear code; comments that explain _why_, not _what_ - **Formatting**: Consistency aids understanding; typography conveys meaning ## Instructions 1. **Check Names**: Are variable/function/class names meaningful and pronounceable? Do they reveal intent? 2. **Analyze Functions**: Does each function do one thing? Can the body fit on one screen? Are parameters minimal (0-3)? 3. **Inspect Duplication**: Is code repeated? Can it be extracted to a single source of truth? 4. **Review Comments**: Are there comments explaining _why_ decisions were made? Remove comments that explain _what_—rewrite the code instead. 5. **Verify Error Handling**: Are errors caught and handled appropriately? Are error conditions clear? 6. **Check Formatting**: Is indentation consistent? Are blank lines used to separate concepts? Are lines < 120 chars?
Details
- Skill name
clean-code-review- Repository
- sethdford/claude-skills
- Path
engineer/code-quality/skills/clean-code-review/SKILL.md- License
- MIT
- Repo updated
- 11 March 2026
FAQ
What does the Clean Code Review skill do?
Systematic code review checklist for readability, maintainability, and correctness. Use when reviewing pull requests or assessing existing code.
How do I install the Clean Code Review 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 Clean Code Review 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.
Cloud Architecture
48sethdford/claude-skills
Design cloud infrastructure for AWS, GCP, or Azure. Plan compute, storage, networking, and compliance. Use when architecting cloud systems or migrating to cloud.
Card Sort Analysis
48sethdford/claude-skills
Analyze card sorting results to inform information architecture and navigation structure. Use after conducting open or closed card sort studies.
Code Complexity Analysis
48sethdford/claude-skills
Measuring and reducing cyclomatic complexity and cognitive complexity to improve maintainability.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.