requesting-code-review

Automating code review before merging involves dispatching a specialized subagent to verify implementation against plans and identify bugs. This Skill triggers that process by using git commands to find commit ranges and applying a structured markdown template for the review criteria.

A subagent-driven development workflow for quality assurance dispatches a specialized code-reviewer to check implementations against requirements. It integrates review at critical junctures like task completion or pre-merge checks to prevent cascading issues and improve code health.

Automated code review verifies implementation against requirements by dispatching a code-reviewer subagent with a structured markdown template. The subagent checks the current changes against the task requirements to identify architectural flaws and deviations early.

Yes, you need git to run this automated pre-merge code review. The process requires git commands to identify the specific commit ranges of your current changes, which the code-reviewer subagent then analyzes against the structured template criteria.

You should request a code review in a development workflow at critical junctures like task completion, feature implementation, and pre-merge checks. Dispatching the review at these stages ensures implementations meet requirements and quality standards before proceeding.

The best way to identify bugs and architectural flaws during feature implementation is dispatching a specialized subagent for proactive issue detection. It checks the code against task requirements and structured criteria to catch deviations early in the development cycle.