requesting-code-review

Automating code review before merging involves dispatching a subagent to compare commit changes against requirements and best practices. This Skill uses git commands and markdown templates to deliver structured feedback on code quality, architecture, and testing compliance.

Ensuring code quality and adherence to standards requires automated checks that compare commit changes against predefined criteria. This Skill dispatches a subagent to review code architecture and testing compliance, providing structured feedback before you merge into the main branch.

Yes, you need git installed to run automated code reviews with this Skill. It requires executing git commands to identify commit ranges and the ability to execute markdown templates to generate structured feedback on your code changes.

Automated code review handles structured feedback by dispatching a subagent that evaluates your commit changes against predefined criteria. It delivers targeted feedback on code quality, architecture, and testing, ensuring your feature branch meets standards before merging.

Yes, you can request a code review for specific git commits by identifying the commit range. You run git rev-parse commands to get the commit hashes, fill in the markdown template, and the Skill evaluates those specific changes against best practices.

A limitation of automated code review is that it depends on predefined criteria and markdown templates to evaluate changes. It requires git execution capabilities and focuses on code quality and standards adherence, meaning complex architectural decisions may still require manual human evaluation.