code-review-and-qualitycommit 28f435eSKILL.md · Code Review
Code Review and Quality
Reviews code changes across five axes, correctness, readability, architecture, security and performance, labeling each finding by severity.
npx skills add addyosmani/agent-skills --skill code-review-and-qualityCommand selected. Copy it manually.
- Permissions
- read-repo
- write-files
- shell
- network
- Compatible with
- Claude Code, Codex, Cursor, Copilot, Gemini CLI
- GitHub
- 112.3k
- Source
- Community · Addy Osmani
- Status
- Scan passed
- License
- MIT
- Category
- Code Review
Core rule
Approve a change when it definitely improves overall code health, even if it isn't perfect.
Execution Phases
Phase 01Understand the context
Before reading code, establish what the change is for, which spec or task it implements, and the expected behavior change.
Phase 02Review the tests first
Check tests cover behavior and edge cases; invert one condition, run the suite and restore the file, and a mutation that stays green is a finding.
Phase 03Review on five axes
Walk each changed file through the five axes and propose a named structural remedy for any structural problem.
Phase 04Label severity
Label each comment Critical, Nit, Optional, FYI or no prefix, and lead with correctness and security.
Phase 05Verify the verification
Check which tests ran, whether the build passed and manual testing was done; list dead code and ask before deleting it.
Permissions (summarised from SKILL.md)
| Capability | Needed | Details |
|---|---|---|
| File writes | Limited | Only temporary mutations restored from a copy, and deleting dead code after asking. |
| Command execution | Limited | Runs the test suite and build to verify the change and for mutation checks. |
| Network outbound | Not required | The review process itself needs no network access. |
SKILL.md frontmatter (YAML)
---
name: code-review-and-quality
description: Conducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensions before it enters the main branch. Use when asked to review a diff or a pull request, even when the diff is pasted inline.
---