requesting-code-review

Automated code review for git changes is facilitated by dispatching specialized subagents to evaluate branch differences against defined project requirements. This process enforces structured quality verification before merging features or proceeding to subsequent development tasks.

Preventing technical debt during development workflow requires enforcing objective, context-specific code reviews before merging. Dispatching a reviewer subagent to check git changes against project plans ensures alignment and stops architectural debt from cascading.

A subagent evaluates code quality by analyzing specific git ranges alongside provided task requirements. It categorizes feedback into Critical, Important, and Minor issues, ensuring objective verification and precise alignment with the defined project plan.

You can categorize code review feedback by severity because the review process classifies issues into Critical, Important, and Minor tiers. This quality gate mechanism helps developers prioritize fixes effectively before completing the development task.

Automated code review works with feature branches by targeting the specific git ranges between the current branch and the main branch. The dispatched subagent uses this context to ensure the feedback remains focused and relevant to the changes.