requesting-code-review

To automate code review for a git commit range, you provide the base and head commit SHAs to dispatch a subagent that analyzes changes against requirements and categorizes issues by severity.

Yes, you can get structured feedback on code quality and architecture before a merge by dispatching a subagent that evaluates production readiness and categorizes issues into Critical, Important, and Minor severities.

The best way to ensure code changes meet original requirements is to trigger a code review subagent that analyzes the git commit range and verifies adherence, providing actionable feedback on testing and architecture.

Yes, you need specific base and head git commit SHAs to trigger a development workflow code review, as these parameters define the exact scope of code changes the subagent analyzes.

Identified code quality issues are categorized by severity into Critical, Important, and Minor classifications, providing structured and actionable feedback on architecture, testing, and overall production readiness.