# /code-review-and-quality: Five-axis code review with clear severity labels

Source: https://trendhub.net/skills/addyosmani-agent-skills/code-review-and-quality
Skill folder: https://github.com/addyosmani/agent-skills/tree/main/skills/code-review-and-quality
Pack: Addy Osmani's Agent Skills (https://trendhub.net/skills/addyosmani-agent-skills)
Works with: Claude Code, Any agent via the skills CLI, Codex, Gemini CLI, Antigravity CLI, Command Code

This skill has the agent review any change, whether written by you, another model or itself, for correctness, readability, architecture, security and performance. It reads the tests first, checks them by flipping a condition, labels each comment as required, critical, optional, nit or FYI, proposes a concrete restructuring for structural problems and reviews dependency upgrades one package at a time.

## When to use it

- A pull request or local diff needs a verdict before merge.
- Another agent or model wrote code you have not examined.
- A bulk dependency bump or a refactor claims to make things cleaner.

## How it works

1. **Understand intent**: The agent works out what the change is meant to do and which spec or task it implements before reading code.
2. **Test the tests**: It reads the tests first, then inverts a condition the change adds and reruns the suite; a test that stays green is reported as a gap.
3. **Walk five axes**: Each changed file is checked for correctness, readability, architecture, security and performance, including size of the diff and of the file.
4. **Label and order findings**: It drops findings that callers or tests rule out, separates old defects from new regressions, tags severity and puts the highest-impact issues first.
5. **Check verification**: It confirms which tests and builds were run and lists any now-unused code, asking before deleting it.

## What it steers the agent away from

- Approving with LGTM and no evidence of review
- Refactors that move complexity around without removing any
- Merging a mass version bump without reading changelogs or the lockfile diff

## What it can touch

Reads the diff, tests and lockfile, runs the test suite and build, and temporarily edits a file to test a mutation before restoring it from a copy.

## Pairs well with

- `/code-simplification`
- `/performance-optimization`
- `/security-and-hardening`

## Questions

### Is a review with no findings acceptable?

Yes. The skill says zero findings is a valid result and the agent should not invent issues to fill the report.

### How large should a change be?

It treats about 100 changed lines as ideal, about 300 as acceptable for one logical change, and around 1000 as a signal to split.
