requesting-code-review

Automating code review requests involves dispatching a code-reviewer subagent to analyze git commit changes against requirements and categorize issues by severity before merging branches. This process checks code quality and feature completeness automatically.

A subagent-driven development workflow dispatches an automated code-reviewer subagent to perform quality assurance checks on completed tasks. It provides structured feedback on code changes, ensuring production readiness before proceeding to the next development phase.

To request a code review for a git commit range, you dispatch the code-reviewer subagent against the specified commits. The subagent then analyzes the code changes, identifies issues by severity, and returns structured feedback for merge readiness.

Automated code review works with ad-hoc software development tasks, plan execution, and subagent-driven workflows. You can dispatch the code-reviewer subagent after completing any task to get immediate feedback on your implementation before merging.

You need automated code review in your development workflow when you want to ensure code quality, verify feature completeness, and prevent bugs before merging code into main branches. It is crucial for maintaining production readiness across git commits.

The best way to identify code issues by severity before a merge is to dispatch a code-reviewer subagent to analyze your git changes against specified requirements. This ensures structured feedback and prevents bugs from entering main branches.