requesting-code-review

Standardize code reviews by dispatching subagents to evaluate changes against defined requirements and quality benchmarks. This enforces consistent, severity-categorized feedback to catch bugs early and prevent architectural drift in complex projects.

Automated code review ensures context-aware evaluation by focusing strictly on changes between two Git commit SHAs. This prevents reviewers from analyzing irrelevant session history and keeps the feedback targeted to the specific feature implementation.

Yes, Git commit history access is required to perform structured code reviews. The review process dispatches subagents to evaluate specific changes between commits, meaning accurate Git SHAs are necessary to scope the evaluation and generate severity-categorized feedback.

Categorize code review feedback by forcing reviewers to distinguish between critical bugs, important architectural issues, and minor stylistic improvements. This severity categorization standardizes pre-merge verification and ensures critical problems are prioritized before merging.

Yes, you can use subagents to automate quality assurance for task completion. The process uses a structured prompt template to dispatch subagents that evaluate code changes against quality benchmarks, ensuring consistent verification across task completion workflows.