requesting-code-review

Automate code review by dispatching a specialized subagent to evaluate code changes against defined requirements and architectural standards. Provide the base and head git commits to generate diffs for comparative analysis.

A subagent evaluates code changes by comparing generated git diffs against a structured plan or requirement document. It analyzes the differences to verify if the implementation matches the defined architectural standards and testing requirements.

You can categorize code review feedback by severity because the subagent automatically classifies issues into Critical, Important, and Minor categories. This severity categorization helps prioritize developer effort during the review process.

You need a structured plan or requirement document for automated code review because the subagent requires it for comparative analysis against the actual code changes. Git history access is also required to generate the necessary diffs.

The best way to ensure production-ready code is to trigger an automated code review subagent after feature implementation. It verifies that the implementation matches the design plan and adheres to testing and architectural standards before merging.

A limitation of using a subagent for code review is that it requires both git history access to generate diffs and a structured requirement document for comparative analysis. Without these inputs, the automated review cannot evaluate architectural standards.