requesting-code-review

Automating code review before merging involves dispatching a specialized subagent to analyze code changes against requirements and quality standards. This process facilitates early detection of critical, important, and minor issues across code quality, architecture, and testing.

Subagent-driven code quality assurance is a workflow where a specialized subagent is dispatched to perform code reviews based on defined criteria. It integrates into development workflows to provide categorized feedback with clear action items after feature completion.

You integrate automated code analysis by dispatching the code-reviewer subagent after completing tasks, features, or before merging. It analyzes changes between the current commit and the main branch to identify bugs, architectural flaws, or missed requirements.

Categorizing code review feedback by severity is supported through structured feedback output. The review process provides categorized feedback across Critical, Important, and Minor levels with clear action items for each identified issue.

Yes, the code review subagent checks requirement adherence by analyzing code changes against defined requirements and quality standards. It evaluates code quality, architecture, testing, and requirement adherence to ensure production readiness before merging.

You should dispatch a code review subagent after completing a complex feature, finishing a task, or before merging changes into the main branch. This ensures continuous quality assurance throughout the development and plan execution workflows.