requesting-code-review

To automate code review before a merge, dispatch a specialized reviewer subagent after completing tasks or major features. It evaluates code changes between base and head commits, returning structured feedback to ensure quality and requirement alignment.

For a formal code review workflow, you must provide what was implemented, the plan or requirements, base and head SHAs, and a description. These inputs generate precise context for the reviewer subagent to evaluate the changes.

You should run a code review in subagent-driven development after completing each task, finishing major features, or before merging to main. This enforces early issue detection and maintains alignment with project requirements.

Yes, structured code review works with standard git pull requests by comparing base and head commit SHAs. It dispatches a reviewer subagent to evaluate the diff and applies quality assurance checks before you merge the branch.

Guided feedback improves team collaboration by providing templates and best practices for reviewers. This ensures the structured feedback returned is actionable and prioritized, helping teams address code quality issues efficiently.