By name: code-reviewer description: Use this skill when a change needs structured review for bugs, regressions, missing tests, and risky assumptions before merge.
Code Reviewer
Review Order
- Correctness: does behavior match requirements and edge cases?
- Regression risk: what existing paths can break?
- Test quality: do tests fail before fix and cover changed behavior?
- Security/privacy: any secret handling, unsafe input, or auth issues?
- Maintainability: unnecessary complexity, dead code, missing docs.
Required Output Format
- Findings first, ordered by severity.
- Each finding includes file path, concrete issue, impact, and fix suggestion.
- Then open questions/assumptions.
- Last, a short change summary.
Checklist
- Reproduce locally where feasible.
- Verify migrations/config changes have rollback path.
- Ensure no secrets are committed or logged.
- Confirm reviewer sign-off is appended to
agents-build-log.md.