requesting-code-review

Dispatch a code-reviewer subagent to review your implementation against requirements. Gather git SHAs for your changes, summarize what you implemented and the original plan, then use the code-reviewer template to generate structured feedback covering code quality, architecture, testing, and production readiness.

Request code review after completing major features, before merging to main as a mandatory quality gate, after subagent-driven tasks, or when stuck or planning refactoring. Early review catches architectural issues and bugs before they cascade into production.

The code-reviewer subagent produces structured feedback covering code quality, architectural soundness, test coverage, severity-based issue categorization, and a production-readiness assessment to help you address problems before deployment.

Yes, you can dispatch a code review before refactoring to get objective feedback on your planned changes. This helps catch potential issues in your refactoring approach before implementation begins.

Provide a summary of what was implemented, the original plan or requirements, base and head git SHAs showing your changes, and a brief description. The code-reviewer subagent uses this context to evaluate your work against requirements.

Yes, code review is applied after each subagent-driven task to ensure work meets requirements before proceeding. This integrates review as a standard step in the development workflow alongside automated implementations.