requesting-code-review

To automate code review, dispatch a code-review subagent with base and head SHAs to validate implementations against your plan. This routes changes to a specialized reviewer that uses structured prompts and templates to generate actionable feedback.

You should run an automated code review after completing each task, after finishing major features, and before merging to main. This ensures quality gates are met and catches issues at key milestones before they cascade.

You need to provide the base and head SHAs to dispatch the code-review agent. These inputs allow the agent to identify the changes and validate the implementation against the original plan using a structured review checklist.

A structured checklist standardizes feedback by enforcing consistent validation of implementations against the plan. It guides the code-reviewer subagent to generate actionable feedback, ensuring quality gates are met before merging to main.

Yes, you can dispatch a code-review subagent to validate major feature implementations before merging to main. It enforces a structured review checklist and compares the head SHA against the base SHA to generate actionable feedback.