| name | requesting-code-review |
| description | Use when completing tasks, implementing major features, or before merging to verify work meets requirements |
Requesting Code Review
Dispatch a code reviewer subagent to catch issues before they cascade.
Core principle: Review early, review often.
When to Request Review
Mandatory: After each task in subagent-driven development, after completing major feature, before merge to main.
Optional: When stuck, before refactoring, after fixing complex bug.
How to Request
- Get git SHAs (BASE_SHA and HEAD_SHA)
- Dispatch code reviewer subagent with template
- Act on feedback: Fix Critical immediately, Fix Important before proceeding, Note Minor for later
Integration with Workflows
Subagent-Driven Development: Review after EACH task.
Executing Plans: Review after each task or at natural checkpoints.
Ad-Hoc Development: Review before merge.
Red Flags
Never: Skip review because "it's simple", ignore Critical issues, proceed with unfixed Important issues.