requesting-code-review

To route code changes through a code review before merging to main, use a dedicated code-review subagent to evaluate production readiness, summarize strengths and issues, and provide structured feedback with fix guidance. This ensures changes meet requirements before integration.

A subagent-based code review process uses a dedicated subagent to evaluate code changes after tasks, major features, or before merging. It applies standardized prompts and severity criteria to produce structured feedback on production readiness.

To evaluate code readiness for merge, apply severity levels like Critical, Important, and Minor to identified issues. The code-review subagent summarizes these issues alongside strengths to determine if the changes are ready for production integration.

You should request a code review after completing each task, when finishing major features, and before merging changes to the main branch. This routing ensures continuous evaluation of production readiness throughout the development workflow.

Yes, you can integrate a subagent-based code review into daily development workflows and governance. It provides standardized templates and clear evaluation criteria to catch issues early and ensure changes meet requirements before integration.

No, the code review process does not require specific dependencies to work. It operates by identifying and routing code changes through a dedicated subagent using standardized prompts to generate structured feedback on strengths, issues, and merge readiness.