requesting-code-review

Coordinate a code-review subagent to generate structured review reports from git diffs.

103|30|Updated Dec 24, 2025

Search Tags:#automation #git #quality #merge #subagent #code-review

Ready to run

npx skills add https://github.com/CommandCodeAI/agent-skills --skill requesting-code-review-commandcodeai

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the code-review feedback loop by orchestrating a dedicated code-review subagent to catch issues early and before merging.

Core Features & Use Cases

Dispatch a code-reviewer subagent after each task to evaluate changes.
Capture WHAT_WAS_IMPLEMENTED, PLAN_OR_REQUIREMENTS, BASE_SHA, HEAD_SHA, and DESCRIPTION to structure the review.
Provide a blueprint for acting on feedback and deciding when to proceed or pause.

Quick Start

Use the requesting-code-review skill to trigger a subagent review after you complete a task, supplying the required placeholders and the final description of 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 reviews before merging to main?▼

You can automate code reviews by dispatching a dedicated subagent that evaluates changes using git SHAs to generate diffs and validates alignment with your plan before merging to main.

What is the best way to structure a code review for feature work and bug fixes?▼

The best way to structure a code review is to capture WHAT_WAS_IMPLEMENTED, PLAN_OR_REQUIREMENTS, BASE_SHA, HEAD_SHA, and DESCRIPTION, which coordinates the reviewer subagent to output a structured report.

How does a subagent generate a code review report from git diffs?▼

A subagent generates a code review report by taking the BASE_SHA and HEAD_SHA to produce a git diff, evaluating the changes against provided requirements, and outputting a structured review for production-ready decisions.

Can I use this automated code review after each task in subagent-driven development?▼

Yes, you can dispatch the code-review subagent after completing each task in subagent-driven development, across both feature work and bug fixes, to catch issues early before merging.

Do I need to provide a description of changes to trigger an automated code review?▼

Yes, you need to supply the required placeholders including the final description of changes, along with the git SHAs and plan requirements, to trigger the subagent review successfully.