requesting-code-review

Automated code review for git commits is facilitated by dispatching a specialized subagent to analyze code changes against implementation details and project requirements. The skill requires git commands to define the review range and uses a templated markdown file for instructions.

Severity-based feedback in a code review workflow works by categorizing identified issues into Critical, Important, and Minor classifications. This structured categorization allows developers to prioritize action on potential bugs and quality issues before submitting a pull request.

Yes, you can use a subagent to analyze code changes against project requirements. The subagent is dispatched to review the implementation details, ensuring the code changes are thoroughly vetted for quality, adherence to requirements, and production readiness.

The best way to integrate code quality checks into subagent-driven development is to dispatch a code-reviewer subagent for the current commit range. It supports structured feedback categorization and integrates directly into development workflows like plan execution.

Yes, you need to define a git commit range to run an automated code analysis. The skill requires git commands to specify the exact review range, which the subagent then analyzes to identify potential bugs and ensure standards are met.

Limitations of subagent-driven code reviews include the dependency on manually defining the git commit range and the reliance on a templated markdown file for instructions. The analysis is bounded by the specified commit range and the project requirements provided.