requesting-code-review

Automating code review involves dispatching a subagent to analyze changes against quality standards. This Skill streamlines that process by using git commands to identify commit ranges and a markdown template to structure reviewer input before merging.

Verifying code changes against requirements is best handled by dispatching a dedicated subagent. It analyzes your feature implementation iteratively, catching architectural flaws and requirement deviations early in the development workflow before they cascade into production.

Yes, you can use git commands to identify specific commit ranges. The Skill requires these commands to accurately scope the code changes, allowing the dispatched subagent to analyze the correct development workflow iterations against your quality standards.

A subagent analyzes code changes by evaluating them against specified requirements and quality standards. It uses a structured markdown template for reviewer input, catching bugs early and providing feedback to ensure code quality before merging into the main branch.

Yes, a structured markdown template is required for reviewer input. The template provides a clear framework for the subagent to follow, ensuring the code review process is streamlined and that feedback directly addresses requirement deviations and quality standards.