requesting-code-review

You can automate code reviews by dispatching a specialized subagent to analyze your git commit ranges and verify changes against specified requirements. This provides structured feedback on strengths and issues before merging.

The subagent analyzes code changes by evaluating the specified commit SHAs against your provided implementation details and quality standards. It then outputs categorized feedback covering critical, important, and minor issues.

Yes, the code review workflow supports early and frequent reviews throughout the development lifecycle. You can dispatch reviews for individual tasks, major feature implementations, and pre-merge verification.

The best way to get structured feedback is to dispatch a code-reviewer subagent with specific commit SHAs. It utilizes a structured template to provide categorized feedback on strengths, critical issues, and minor problems.

Yes, you need git commands to identify the commit ranges for review. The skill requires these commit ranges to dispatch the code-reviewer subagent and analyze the corresponding code changes.

You should request code reviews early and frequently throughout the development workflow, from completing individual tasks to finalizing major features and performing pre-merge verification.