requesting-code-review

Automate code review requests by dispatching a review subagent after task completion. You provide the implementation details, plan requirements, and Git base and head SHAs to trigger structured, independent verification before merging.

To dispatch a code review, you need to provide four inputs: WHAT_WAS_IMPLEMENTED, PLAN_OR_REQUIREMENTS, BASE_SHA, and HEAD_SHA. These inputs allow the review subagent to verify alignment between the code changes and the original plan.

Request a code review after completing each task, finishing a major feature, or before merging. Dispatching reviews at these checkpoints catches issues early and prevents defects from cascading into other parts of the project.

The best way to ensure consistent code review feedback is using a template-driven workflow. Standardized review prompts and reviewer guidance maintain quality across tasks by structuring the verification process for every feature.

The review subagent dispatches structured feedback based on the provided SHAs and implementation details. It includes integration guidance to help developers act on the review results and resolve any identified issues before merging.

No, providing the BASE_SHA and HEAD_SHA is required. The Git commit SHAs are essential inputs for the review subagent to identify the exact code changes and perform accurate independent verification against the plan.