| name | code-review-and-quality |
| description | Use when reviewing code before merge to assess correctness, tests, maintainability, security and user impact. |
Code Review and Quality
When to use
Use this skill when reviewing a diff written by yourself, another agent or a human, or when deciding whether a change is ready to merge.
Objective
Identify correctness risks, test gaps, maintainability problems, hidden regressions and security concerns before the change lands.
Procedure
- Read the change in the context of the surrounding code.
- Identify the intended behaviour and any behaviour change.
- Check correctness, edge cases, tests and public contracts.
- Assess maintainability, duplication and naming only after correctness is clear.
- Classify findings by severity and impact.
- Suggest the smallest fix or follow-up needed to close each finding.
Rules
- Do not review in isolation from the code the diff touches.
- Do not let style preferences outrank correctness or safety.
- Do not suppress a real issue just because the diff is small.
- Do not approve a change without checking the relevant tests or evidence.
Related skills
tdd-practice — tests as review evidence
logical-fallacy-review — invalid reasoning in review comments
git-workflow-and-versioning — reviewable atomic changes
guardrails-safety-patterns — security findings in review
References
Verification