requesting-code-review

Automate code-review requests using BASE_SHA and HEAD_SHA with the code-reviewer subagent.

Updated Jan 28, 2026

Search Tags:#automation #workflow #subagent #quality-assurance #code-review #pull-request #review-process

Ready to run

npx skills add https://github.com/kckylechen1/ai-agent-toolkit --skill requesting-code-review-kckylechen1

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/kckylechen1/ai-agent-toolkit/tree/main/skills/requesting-code-review
Command: npx skills add https://github.com/kckylechen1/ai-agent-toolkit --skill requesting-code-review-kckylechen1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the process of requesting and coordinating code reviews to catch issues early and prevent cascading defects as work progresses.

Core Features & Use Cases

Mandatory review automation: Enforces reviews after each task in subagent-driven development.
Pre-merge validation workflow: Applies to major feature completion and before merging to main.
Template-driven collaboration: Uses a standardized workflow with the code-reviewer subagent and the template at code-reviewer.md to structure feedback.
Use Case: After finishing Task 2, trigger a review to validate changes before proceeding.

Quick Start

BASE_SHA=<starting-commit> # replace with actual base HEAD_SHA=<current-commit> # replace with actual head [Dispatch superpowers:code-reviewer subagent] WHAT_WAS_IMPLEMENTED: <brief summary of changes> PLAN_OR_REQUIREMENTS: <reference to task plan or requirements> BASE_SHA: a1b2c3d4 HEAD_SHA: d4c3b2a1 DESCRIPTION: <brief description of implemented changes>

Frequently Asked Questions about requesting-code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate code review requests for subagent-driven development?▼

Automating code review requests requires dispatching the code-reviewer subagent with your BASE_SHA and HEAD_SHA to catch issues early and prevent cascading defects. This enforces mandatory peer validation after each task completion.

When do I need a pre-merge code review workflow?▼

A pre-merge code review workflow is needed for major feature completion and before merging to main. It validates changes after completing tasks in subagent-driven development to prevent cascading defects from progressing downstream.

What inputs do I need to run an automated pull request review?▼

Running an automated pull request review requires capturing the BASE_SHA starting commit, HEAD_SHA current commit, a brief summary of implemented changes, and a reference to the task plan or requirements before dispatching the code-reviewer subagent.

How does the code-reviewer subagent structure pull request feedback?▼

The code-reviewer subagent structures pull request feedback using a standardized template at code-reviewer.md, categorizing issues into Critical, Important, and Minor severity levels for acting on feedback before proceeding with merges.

Does this code review automation work without external dependencies?▼

This code review automation works without external dependencies, relying solely on dispatching the code-reviewer subagent and providing commit SHAs to enforce quality assurance in subagent-driven development workflows.