requesting-code-review

Automating code review before a merge involves dispatching a subagent to validate changes using base and head commit SHAs. This process requires a structured request detailing what was implemented and the original plan to produce a readiness assessment.

Subagent-driven development for quality assurance dispatches a code-reviewer subagent to validate changes after individual tasks or major features. It provides structured feedback including strengths, issues by severity, and a pre-merge readiness assessment.

Requesting a code review with git commit SHAs requires providing the BASE_SHA and HEAD_SHA alongside a description, implementation details, and requirements. This structured template dispatches a subagent to evaluate code quality and readiness.

Yes, a pre-merge readiness assessment for code quality and architecture is generated by dispatching a code-reviewer subagent. It evaluates structured inputs including implementation details and commit SHAs to output a clear merge decision.

You should dispatch a code-reviewer subagent after completing each task in subagent-driven development, after finishing major features, and before merging code to the main branch to ensure early detection of issues.

No, automated code review requires plan or requirements documentation as part of its structured request template. Providing the PLAN_OR_REQUIREMENTS alongside commit SHAs and implementation details is necessary to generate accurate feedback.