requesting-code-review

To get a structured code review before merging, you provide the base and head git SHAs along with implementation context to a dedicated subagent, which then returns severity-ranked feedback and a merge readiness assessment.

A subagent-driven code review workflow dispatches a dedicated review subagent over a bounded git SHA range, ensuring the agent evaluates the specific work product rather than your full session history.

You request a code review for a specific git diff range by capturing the base and head commit SHAs, filling the review template placeholders with requirements context, and dispatching the review subagent.

You should request a pre-merge code review for production readiness after completing subagent tasks, finishing major features, and validating requirements before merging to main.

Severity-ranked feedback categorizes identified issues into Critical, Important, and Minor levels, providing a clear merge readiness assessment so you can follow a structured fix-or-note workflow.

No, providing implementation and requirements context by filling the review template placeholders is required for the subagent to accurately check architecture, requirements, and testing.