requesting-code-review

Capture the base and head git SHAs for your change range, then dispatch a general-purpose subagent using the code-reviewer template with the description, requirements, and SHAs filled in. 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 as a baseline check, or after fixing a complex bug.

The reviewer needs a brief description of what was built, the plan or requirements it should satisfy, and the base and head commit SHAs defining the diff range. It should never receive your full session history, only precisely crafted context.

No. The template enforces a read-only review using git show, git diff, and git log. If another revision must be inspected, the reviewer uses a separate git worktree in a temporary directory rather than moving HEAD on your checkout.

Push back with technical reasoning and show code or tests that prove the implementation works. You can also request clarification, but never ignore valid Critical or Important issues without addressing them.