requesting-code-review

To automate a production-readiness code review, you provide the base and head git SHAs along with the implementation details to a reviewer subagent. The subagent validates the changes against your requirements and provides a structured merge readiness assessment.

Subagent-driven code review uses a dedicated reviewer agent to validate implemented changes against your original plan. You need it after completing subagent-driven development tasks, major features, refactors, or any pre-merge checkpoint to catch bugs and test gaps.

Categorizing code review issues by severity involves sorting findings into Critical, Important, and Minor buckets. This structured feedback forces critical fixes before proceeding and requires technical justification if you choose to push back on the reviewer's assessment.

Yes, you can request a code review using git base and head SHAs. You must also fill out a review template detailing what was implemented and what it was supposed to do, allowing the reviewer subagent to validate the exact diff against your requirements.

The best way to validate architecture and test gaps in batch execution plans is to dispatch a dedicated reviewer subagent. It checks the implemented changes against the original requirements and categorizes any discovered architecture issues or test gaps by severity.

Production-readiness code review works for both major refactors and new features. It applies to any pre-merge check or subagent-driven task, validating that the implemented changes align with the plan and identifying architecture issues before merging to main.