requesting-code-review

To automate code review before merging, you provide the base and head Git commit SHAs with a brief implementation description, dispatching a subagent to assess code quality and compliance. This enforces a systematic review step for early feedback.

You should request a code review during feature development after completing a task, finishing a major feature, or before merging to main. This timing ensures early feedback and maintains high code quality before integration.

To get a code review for recent Git changes, you need to provide the base and head commit SHAs defining the changeset, along with a brief description of the implementation for the subagent to assess against requirements.

Yes, this code review automation integrates into subagent-driven development workflows by automatically capturing Git commit ranges and dispatching the code-reviewer subagent with a structured template for continuous quality assurance.

Using an automated subagent for code reviews enforces a systematic review step that developers often skip or postpone, automatically gathering commit ranges and comparing implementations against requirements to prevent bugs and technical debt.