requesting-code-review

Automating code review before merging a pull request requires dispatching a reviewer subagent to evaluate implementation against the plan, inspect code quality, architecture, tests, and production readiness, generating a structured report with base and head SHAs.

Subagent-driven development uses specialized agents for tasks, where code review fits by dispatching a subagent after each completed task to validate implementation against predefined criteria, ensuring structured evaluation and early issue detection before integration.

To generate a structured code review report for git commits, provide a task summary to trigger the reviewer subagent, which evaluates completed work and produces a template-ready report including base and head SHAs for precise tracking.

Yes, you can use a code review subagent to check production readiness by dispatching it to inspect code quality, architecture, and tests, ensuring critical issues are surfaced before integration into the main branch.

The best way to catch code quality issues early is to request a code reviewer after completing major features or before merging to main, applying structured review templates to evaluate the implementation thoroughly.

Yes, the code review approach works without external dependencies, relying solely on a dispatched subagent to compare implementation against the plan and produce a template-based report for quality assurance.