requesting-code-review

You can automate code review before merging by dispatching a code-reviewer subagent with the git BASE_SHA, HEAD_SHA, implementation description, and plan reference to evaluate production readiness.

A structured code review checklist for production readiness evaluates code quality, architecture, testing, requirements alignment, and severity-classified issues to provide actionable file:line remediation guidance.

To get file and line specific feedback, provide the git base/head range and implementation context to a code-reviewer subagent, which returns severity-classified issues with actionable remediation guidance.

Yes, focused subagent dispatch sends only the relevant git range and implementation context to the code-reviewer, preventing session history leakage during the production readiness review.

You should request a subagent-driven code review after completing each subagent task, before merging major features, or when stuck on complex bugs to get actionable feedback.

Automated subagent code reviews require a specific git base/head range and implementation context, relying on a structured checklist to evaluate production readiness without accessing broader session history.