requesting-code-review

Capture the base and head git SHAs for your change range, then dispatch a general-purpose subagent using the code-reviewer.md template filled with a description, requirements, and the two SHAs. The reviewer returns categorized issues and a merge verdict.

Request review after each task in subagent-driven development, after completing a major feature, and before merging to main. It is also valuable when stuck, before refactoring for a baseline check, or after fixing a complex bug.

The reviewer checks plan alignment, code quality, architecture, testing, and production readiness. It performs a read-only review using git diff and git log, and reports strengths plus Critical, Important, and Minor issues with file:line references.

Push back with technical reasoning rather than accepting incorrect feedback. Show code or tests that prove the implementation works, and request clarification from the reviewer when its assessment conflicts with evidence.

Reviewing the diff inline consumes the context window needed to coordinate the overall work. A subagent keeps the diff and evaluation in its own context, returning only the findings so you can keep driving the work.