requesting-code-review

Dispatch code review subagents with focused context to catch issues before they compound.

- Integrates with subagent-driven development workflows, triggering review after each task or before merging to main

- Provides code-reviewer subagent with precise git SHAs, implementation details, and requirements, keeping reviewer focused on work product rather than session history

- Categorizes feedback into Critical (fix immediately), Important (fix before proceeding), and Minor (note for later) severity levels

- Includes template-based dispatch mechanism using Task tool with placeholders for implementation summary, requirements, commit range, and description

Requesting Code Review

Dispatch a code reviewer subagent to catch issues before they cascade. The reviewer gets precisely crafted context for evaluation - never your session's history. This keeps the reviewer focused on the work product, not your thought process, and preserves your own context for continued work.

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 but valuable:

- When stuck (fresh perspective)

- Before refactoring (baseline check)

- After fixing complex bug

How to Request