requesting-code-review

To automate code review before merging, this Skill dispatches a code-reviewer subagent to validate changes against project standards using a standardized template. It assesses code quality, architecture, testing, and production readiness across your specified git range.

The best way to validate code quality after major feature completion is triggering a structured review subagent. It compares your implementations against the target plan and evaluates architecture, testing, and production readiness before you merge.

Subagent code review works by dispatching a specialized agent to assess a specified git range (BASE_SHA to HEAD_SHA). It applies a standardized review template to evaluate code quality, architecture, testing, and production readiness before merging.

Yes, you need to provide a specific git range from BASE_SHA to HEAD_SHA to trigger an architecture review. This range allows the code-reviewer subagent to accurately identify changes and validate them against your project standards.

Yes, you can use this pre-merge code review across different development cycles. It is designed to trigger after each task, after major feature completion, and before merges to ensure early detection of issues.

A standardized code review template assesses code quality, architecture, testing, and production readiness. It ensures your changes align with project standards and the target plan before allowing a merge.