requesting-code-review

Automated code review before merging is achieved by dispatching a specialized subagent to evaluate the git range. You provide a BASE_SHA, HEAD_SHA, and a review plan to receive a structured assessment of code quality, architecture, testing, and merge readiness.

To trigger a code review, you need to provide a git range from BASE_SHA to HEAD_SHA and a clear review plan or template. The subagent uses these inputs to evaluate work and output a formal assessment of production readiness.

You should run an automated code review after each task in subagent-driven development, after completing major features, and before merging to main. This ensures issues are caught early and context is preserved before final integration.

Yes, automated code review evaluates production readiness and testing. The dispatched subagent generates a formal assessment covering code quality, architecture, testing, and overall merge readiness based on the provided git diff.

The best way to preserve context during pre-merge code evaluations is to dispatch a dedicated code-reviewer subagent. This subagent focuses exclusively on the provided git range and review plan, ensuring focused assessment without losing developmental context.