requesting-code-review

Run a pre-merge code review by dispatching a dedicated code-reviewer subagent to evaluate unmerged changes against requirements, categorizing defects by severity to prevent post-merge rework.

Severity-categorized feedback classifies code review issues as Critical, Important, or Minor, providing clear remediation guidance to enforce quality assurance standards before merging.

Request a structured code review after implementing major features, completing subagent-driven development, or performing ad-hoc pre-merge validation to catch security gaps and technical debt.

Yes, the code review skill assesses production readiness by evaluating code changes against quality standards, identifying missing error handling or compliance gaps before the code reaches production.

Subagent-driven development integrates with code quality validation by dispatching a code-reviewer subagent at review checkpoints to enforce guardrails and catch undetected defects early.

Automated pre-merge validation focuses on structured code review feedback and production readiness assessment, requiring formal review checkpoints to catch quality gaps that automated tests might miss.