requesting-code-review

Automating code review before a git merge requires dispatching a specialized subagent to analyze code changes against specified requirements. This skill provides a predefined template to submit git SHAs and project requirements for evaluation.

Subagent-driven code review is a process where a specialized code-reviewer subagent analyzes your code changes against requirements. It automates quality assurance by evaluating commit history and providing structured feedback to catch issues before merging.

To request a code review, obtain the relevant git SHAs and fill out a predefined code-reviewer template with your requirements. The skill then dispatches the subagent to analyze the changes and return structured feedback.

Yes, you can use this automated code review for subagent-driven development workflows. It is specifically designed to support plan execution and subagent-driven development by facilitating early and frequent reviews to catch issues before merging.

You should act on code review feedback by following a phased approach based on severity levels. The skill guides users to address Critical, Important, and Minor feedback differently to ensure code quality before merging.

Yes, you need specific git commit SHAs to run an automated code review. The skill requires obtaining these git SHAs and filling a predefined template to provide the subagent with the exact changes for analysis.