requesting-code-review

Automated pre-merge code review routes code changes to a dedicated subagent to validate implementation against the plan before merging to main. This dispatching mechanism is triggered automatically after task completion to catch regressions early.

Automated code review should be triggered after each subagent-driven task, after major features are completed, or directly before merging to main. This timing ensures issues are identified early and feedback is provided before code changes are integrated.

A subagent-driven workflow operates by dispatching a code-review subagent using standardized templates with placeholders like BASE_SHA, HEAD_SHA, and WHAT_WAS_IMPLEMENTED. This ensures consistent validation of code changes against defined requirements.

Automated code review templates require specific placeholders: WHAT_WAS_IMPLEMENTED, PLAN_OR_REQUIREMENTS, BASE_SHA, HEAD_SHA, and DESCRIPTION. Providing these details ensures the subagent accurately validates your latest commit against the original plan.

Automated code review dispatches a subagent to validate your implementation against the defined plan or requirements. By providing the base and head SHAs along with the plan details, it checks code changes for consistency before merging.

Pre-merge quality assurance automation requires no external dependencies, operating entirely within the Task tool's workflow. It integrates natively by routing changes to a code-review subagent using a standardized template.