requesting-code-review

Automate code review by dispatching a specialized subagent to analyze git changes against implementation details and requirements. The subagent identifies critical issues, catches bugs, and verifies adherence to plans before merging. You define the review range using git commands and provide a templated markdown file for input.

The best way to check code quality is to dispatch a code-reviewer subagent that proactively detects architectural flaws and requirement deviations. This approach catches bugs early by analyzing code changes against original requirements, ensuring project integrity before merging to the main branch.

Yes, automated code review integrates seamlessly into iterative development workflows. After completing a new feature, dispatch the code-reviewer subagent to analyze changes against original requirements, identifying critical or important issues before merging to the main branch.

Yes, you need git commands to define the review range and a templated markdown file for the reviewer's input. These inputs allow the specialized subagent to analyze code changes against implementation details and requirements before merging.

A code review subagent identifies bugs, architectural flaws, and requirement deviations in your code changes. By analyzing changes against implementation details and requirements, it ensures code quality and catches critical or important issues before merging to the main branch.

Use an automated subagent for code review when you need to verify adherence to plans and catch critical issues before merging. It streamlines the process by analyzing code changes against requirements, preventing bugs and maintaining project integrity in subagent-driven development workflows.