requesting-code-review

To automate code review before a git merge, you can dispatch a code-reviewer subagent to analyze changes within a specified commit range. This process categorizes identified issues into critical, important, and minor severity levels to ensure code quality.

Proactive code quality assurance involves analyzing code changes against specified requirements to identify issues before merging. It works by dispatching a specialized agent to review git commit ranges and provide structured feedback on critical, important, and minor issues.

Yes, you need git SHAs for the base and head commits to define the review range. These commit identifiers are required inputs for the code-reviewer subagent to accurately analyze the specific code changes against your requirements.

You can get structured feedback on critical code issues by using an automated review process that categorizes findings by severity. The code-reviewer agent analyzes your git commit range and separates issues into critical, important, and minor levels.

Yes, you can use automated code review to check code changes against specified requirements. By dispatching a code-reviewer subagent to analyze your git commit range, it identifies issues and categorizes them by severity before human review or merging.