requesting-code-review

Automating code review involves dispatching a code-reviewer sub-agent to evaluate git diff ranges against your development plan before merging. This provides structured feedback covering code quality, architecture, testing, and alignment using standardized templates.

Automated peer feedback works by dispatching a code-reviewer sub-agent upon task completion to assess git diff ranges against the original plan. It generates structured feedback covering code quality, architecture, testing, and alignment before merging.

The best way to get structured code feedback is by dispatching a code-reviewer sub-agent to assess git diff ranges using standardized templates. This ensures production-ready feedback covering code quality, architecture, testing, and plan alignment before merge.

Yes, you can use code-reviewer templates to enforce quality gates in iterative workflows. By dispatching a code-reviewer sub-agent before merging, you enable early detection of issues and maintain production-ready quality across task-based development cycles.

No specific external dependencies are required to validate code changes against a plan. The process relies on invoking a dedicated code-reviewer sub-agent and using structured templates to evaluate your git range references before merging code.

Using an automated code reviewer preserves developer context and ensures feedback focuses on outcomes by standardizing the evaluation of git diffs against your plan. It provides consistent, structured feedback on code quality, architecture, and testing before merging.