code-review-and-quality
Conducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a…
What it does
- Before merging any PR or change
- After completing a feature implementation
- When another agent or model produced code you need to evaluate
- When refactoring existing code
- After any bug fix (review both the fix and the regression test)
- Does it match the spec or task requirements?
- Are edge cases handled (null, empty, boundary values)?
Requirements & configuration
- When another agent or model produced code you need to evaluate
- When large changes are acceptable: Complete file deletions and automated refactoring where the reviewer only needs to verify intent, not every line.
- Every change needs a description that stands alone in version control history.
- | "We'll clean it up later" | Later never comes. The review is the quality gate — use it. Require cleanup before merge, not after. |
- | "AI-generated code is probably fine" | AI code needs more scrutiny, not less. It's confident and plausible, even when wrong. |
Derived from the skill's own SKILL.md documentation · extracted 2026-07-23
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.
Source
Repository: https://github.com/addyosmani/agent-skills
code-review-and-quality FAQ
What does the code-review-and-quality skill do?
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. Before merging any PR or change After completing a feature implementation
What does code-review-and-quality require?
When another agent or model produced code you need to evaluate When large changes are acceptable: Complete file deletions and automated refactoring where the reviewer only needs to verify intent, not every line. Every change needs a description that stands alone in version control history. | "We'll clean it up later" | Later never comes. The review is the quality gate — use it. Require cleanup before merge, not after. | | "AI-generated code is probably fine" | AI code needs more scrutiny, not less. It's confident and plausible, even when wrong. |
How do I install code-review-and-quality?
Run: npx -y skills add https://github.com/addyosmani/agent-skills --skill code-review-and-quality --agent claude-code — the source lives at github.com/addyosmani/agent-skills.
Maintain code-review-and-quality?
Let people know it's listed here — add the badge (live metrics, light/dark aware) or a plain link to your README or docs.
[](https://getagentictools.com/skills/addyosmani-agent-skills-code-review-and-quality?ref=badge) npx agentictools info skills/addyosmani-agent-skills-code-review-and-quality The second line is the CLI lookup for this page — handy in READMEs and docs.