requesting-code-review

To automate code review for recent git changes, dispatch a specialized subagent to analyze your code against requirements and quality standards. This process requires establishing a review range using git commands and a structured template for categorizing feedback.

The best way to catch bugs and architectural flaws early in the development workflow is to run an automated code review after completing each task or feature. This identifies potential issues and verifies requirement alignment before code reaches production.

Automated requirement verification works by dispatching a subagent to analyze code changes against specified plans and quality standards. It categorizes feedback into a structured template, ensuring implemented code aligns with functional requirements.

Yes, you need to use git commands to establish the review range for automated code review. Defining the specific commit range allows the analyzing subagent to accurately evaluate only the recent code changes against your quality standards.

You should run an automated code review in an iterative development process after completing each task or feature. This integration ensures continuous quality assurance, catching requirement deviations and bugs before merging to the main branch.

Yes, you can get categorized feedback without manual inspection by using a structured template. The subagent analyzes code changes and outputs organized feedback, highlighting bugs and architectural flaws automatically for quick assessment.