requesting-code-review

To automate code review, you provide the base and head Git SHAs along with your implementation plan. A specialized code-reviewer subagent is then dispatched to analyze the code changes against your requirements and categorize issues by severity.

Requesting a code review requires the Git SHAs for your base and head commits to define the review scope. You also need to provide context about what was implemented and the original development plan to assess requirement fulfillment.

The automated code review process categorizes identified issues into Critical, Important, and Minor severity levels. This structured feedback uses a detailed checklist to assess code quality, architecture, testing, and requirement fulfillment for prioritized action.

Yes, you can use this code review subagent to verify production readiness. It evaluates code changes against defined plans and requirements, ensuring thorough quality checks are completed before merging to prevent bugs and improve code health.

Integrating code quality assurance involves dispatching an automated code-reviewer subagent after completing a feature. By supplying the necessary context and Git commit ranges, the subagent performs a comprehensive assessment of your development workflow changes.