Requesting Code Review

Dispatch code-reviewer sub-agent using the task tool 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
• When the change touches security-relevant code — untrusted input, authn/authz, secrets, injection sinks, subprocess/plugin boundaries, or new dependencies (dispatch security-reviewer)

Optional but valuable:

• When stuck (fresh perspective)
• Before refactoring (baseline check)
• After fixing complex bug