requesting-code-review

Automating code review before merging involves dispatching a subagent to analyze git changes against specified requirements and quality standards. This skill facilitates that structured review process to catch bugs early and ensure code meets architectural guidelines.

Subagent-driven development workflow for quality assurance is a process where a specialized subagent is dispatched to automatically check code changes for bugs and requirement adherence. It integrates directly into development methodologies to prevent issues before merge.

To define the review range for a code review subagent, you need to use standard git commands to specify the commit boundaries. The skill then requires a templated markdown file to provide the reviewer subagent with the necessary input and context.

Yes, you can integrate this code review process with your existing development workflow. It is specifically designed to support integration into various methodologies, including subagent-driven development and plan execution, to ensure quality assurance without disrupting your routine.

You should run an automated code review on your feature branch after completing a complex feature and before you merge your changes. This proactive bug detection step ensures code meets requirements and catches architectural flaws early in the development cycle.