requesting-code-review

Automate code reviews by dispatching a dedicated code-review subagent to analyze your changes. Provide the git diff range (BASE_SHA to HEAD_SHA), your implementation details, and the original plan or requirements. The subagent evaluates code quality, architecture, testing, and requirement adherence, returning categorized feedback with a production-readiness recommendation.

Run code reviews after completing features, after each development task, or before merging to main. Early reviews catch issues before they compound, prevent bugs from reaching production, and ensure alignment with plans. Integrate reviews into your workflow as a quality checkpoint between implementation and merge.

A code review assessment provides structured feedback organized by severity (Critical, Important, Minor), specific file and line references, suggested fixes, identified strengths, and a production-readiness verdict. This categorized output helps you prioritize issues and make informed merge decisions.

Yes, code reviews apply across any subagent-driven development workflow. Whether you're building features, refactoring, or integrating components, dispatch the code-reviewer subagent with your changes, plan, and implementation summary. The review process remains consistent regardless of task type.

Provide WHAT_WAS_IMPLEMENTED (your code changes), PLAN_OR_REQUIREMENTS (original specifications), BASE_SHA and HEAD_SHA (git commit range), and DESCRIPTION (summary of changes). These inputs enable the subagent to evaluate whether your implementation meets requirements and follows best practices.

Code review analyzes implementation against requirements and best practices before merge, identifying bugs, architectural concerns, and quality gaps. Early detection prevents issues from reaching production, reduces debugging effort, and ensures code meets functional and technical standards.