requesting-code-review

A pre-merge code review catches bugs, design flaws, and missing requirements before they reach main by enforcing a deliberate review step. It applies to feature work, bug fixes, and refactors, organizing findings into critical, important, and minor issues with clear guidance on what to fix before merging.

For subagent-driven development, the review process prompts you to request an evaluation after each subagent task. The reviewer evaluates only the work product, not your session history, ensuring feedback stays focused on the implementation summary, requirements alignment, and git range you provide.

A focused code review requires precise git ranges, implementation context, and requirements alignment to assess production readiness. The reviewer evaluates only the work product independently, returning structured severity findings on code quality, architecture, testing, and release risk.

Yes, the code review process applies to feature work, bug fixes, and refactors. It enforces mandatory review checkpoints after major features and before merging, assessing production readiness by returning prioritized, severity-based findings on code quality and release risk.

The code review evaluates only your final work product, not your session history. This focused reviewer context ensures feedback stays sharp and relevant to the implementation summary, requirements, and git range, assessing production readiness independently.