requesting-code-review

To automate code review before merging, you can trigger a reviewer subagent to evaluate code changes against requirements. This dispatches a subagent to produce structured feedback covering code quality, architecture, and testing.

A subagent code review is an automated peer review process where a subagent evaluates code changes. It requires the implemented changes, plan or requirements, and base/head commit SHAs to generate objective feedback on production-readiness.

You request a code review in a task-driven development workflow by executing a review request after completing a task. This action provides the subagent with precise context, including a standardized diff view, to evaluate the work.

For an automated code review, you must provide what was implemented, the plan or requirements, and the base and head commit SHAs. This context ensures the reviewer subagent generates targeted and objective feedback.

Yes, automated code review works for pre-merge checks in git workflows by dispatching a subagent to validate requirements and catch edge cases. It applies to task-driven development and major feature integrations.

Using a subagent for code review focuses on objective feedback for the work product rather than personal context, but it requires specific inputs. You must supply the implementation details, requirements, and commit SHAs to generate a review.