requesting-code-review

Automating code review before merging requires routing changes to a dedicated code-reviewer subagent to validate code quality, architecture, testing, and documentation against the plan. This structured review process provides actionable feedback to satisfy production-readiness criteria.

A pre-merge code review subagent is an automated QA mechanism that assesses task-driven code changes upon completion. It evaluates the code against the original plan and generates reproducible feedback detailing strengths, issues, and recommendations before integration into the main branch.

Automated pre-merge routing is designed specifically for task-based development workflows. Each completed task triggers the formal review subagent, ensuring critical issues are caught and production-readiness criteria are met before merging to the main branch.

The best way to ensure code quality before integration is dispatching a dedicated code-reviewer to evaluate changes. This automated process checks architecture, testing, and documentation, returning structured feedback with actionable recommendations to catch critical issues before merging.

To get structured QA feedback, route your code changes to a code-reviewer subagent after completing a task. The subagent evaluates the changes and provides reproducible feedback containing specific strengths, identified issues, and actionable recommendations.

You need to trigger a formal code review after completing a development task and before merging changes to the main branch. This ensures critical integration issues are caught early by evaluating code quality, architecture, testing, and documentation against the plan.