| name | code-review |
| description | Use when reviewing a diff, pull request, patch, or proposed implementation for bugs, regressions, missing tests, security issues, performance problems, or maintainability risks. |
Code Review
Take a reviewer stance: findings first, grounded in code references.
Priorities
Review for:
- Correctness bugs and behavioral regressions.
- Security and privacy risks.
- Data loss, race conditions, and unsafe migrations.
- Missing or weak tests for changed behavior.
- Performance issues with clear user or system impact.
Do not spend review budget on style preferences unless they hide a real defect.
Process
- Understand the intended behavior and changed surface.
- Read surrounding code before judging the diff.
- Check whether tests cover the changed behavior and failure modes.
- Verify claims against code, not vibes.
- Keep each finding narrow and actionable.
Output
Start with findings ordered by severity. For each finding include:
- Severity.
- File and line.
- Why this can fail.
- A concrete fix direction.
If there are no findings, say that directly and mention remaining test gaps or residual risk.
