requesting-code-review

Automating code reviews for recent git commits involves dispatching a subagent to evaluate changes between base and head SHAs. This skill triggers focused critique on the latest commits using a defined plan and structured feedback template to ensure consistent, actionable results before integration.

A subagent-driven code review workflow dispatches a dedicated agent to generate targeted feedback on recent changes. It evaluates commits against a predefined plan and formal feedback template, ensuring structured and consistent review results for task-driven development.

Pre-merge checks across git branches require base and head SHAs, a defined plan, and a feedback template. This skill dispatches a review subagent to evaluate branch changes against these inputs, enforcing review checkpoints before merging to main branches.

Yes, a formal feedback template is required to automate a code review. The template ensures the subagent generates consistent, actionable, and structured feedback rather than unstructured commentary when evaluating recent commits and tasks.

Yes, automated code review is applicable to major feature work and task-driven development. The subagent evaluates recent changes against a defined plan, providing focused critique to coordinate timely, high-quality reviews in fast-moving software projects.

Automating git code reviews with subagents requires base and head SHAs, a defined plan, and a formal feedback template to function. Without these inputs, the subagent cannot generate the targeted feedback needed for pre-merge governance.