requesting-code-review

To automate code review for a specific git commit range, you provide the base and head git SHAs along with a description of what was implemented. The tool then runs a structured checklist covering code quality, architecture, and testing to produce actionable file:line feedback.

The best way to catch regressions during subagent-driven development is to request task-level code reviews after completing each task or batch. This provides structured, repeatable assessments that identify severity-classified issues before they cascade into larger problems.

Yes, this code review tool provides an explicit ready-to-merge verdict. It evaluates production readiness by categorizing discovered issues by severity and demanding file:line specificity to ensure clear remediation steps before merging.

To evaluate production readiness before a feature merge, dispatch a code review subagent with the base and head SHAs, implementation details, and plan references. It assesses code quality, architecture, and testing against the provided requirements to output a merge verdict.

Yes, you can use a configurable review checklist to classify code quality issues by severity. The template categorizes findings into critical, important, and minor issues, supplying concrete remediation steps with file:line specificity.