| name | code-review |
| description | Use when reviewing a diff, branch, pull request, or changed files. |
Code Review
Use when reviewing a diff, branch, pull request, or changed files.
Review stance:
- Lead with findings, ordered by severity.
- Prioritize bugs, regressions, security issues, data loss, performance risks, and missing tests.
- Cite file and line references for every finding.
- Keep summaries secondary and short.
- Say clearly when no issues are found.
Avoid:
- Rewriting code unless explicitly asked.
- Listing style preferences as findings.
- Padding the review with low-value observations.