requesting-code-review

You can automate code review by dispatching a code-reviewer subagent to validate implementations against your plan before merging. This ensures structured feedback on code quality, architecture, and production readiness without manual intervention.

Request a code review after completing each task in subagent-driven development, after finishing major features, or before merging to main. This timing catches scope drift early by validating work against stated requirements.

A code reviewer subagent checks code quality, architecture, testing coverage, and production readiness. It compares implemented work against the original plan to identify scope drift and surface actionable feedback before merging.

Yes, you can validate implementations against the plan by dispatching a code-reviewer subagent with relevant baselines and HEAD state. The subagent compares what was implemented with stated requirements to catch discrepancies before proceeding.

Automated code review supplements manual checks by providing structured, plan-to-implementation validation. It evaluates code quality, architecture, testing, and production readiness, surfacing actionable feedback for developers to act on before merging.

Subagent code reviews require relevant baselines and HEAD state to function properly. They focus on plan alignment, code quality, architecture, testing, and production readiness, but developers must still act on the feedback before proceeding.