requesting-code-review

Dispatch a reviewer subagent to validate code changes before merging.

14|2|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/gquthier/CLAWG --skill requesting-code-review-gquthier
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/gquthier/CLAWG/tree/main/skills/software-development/requesting-code-review
Command: npx skills add https://github.com/gquthier/CLAWG --skill requesting-code-review-gquthier

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams ensure code quality by dispatching a reviewer subagent and conducting structured reviews to catch issues early.

Core Features & Use Cases

  • Self-review workflow: prompts the author to verify conventions, tests, and documentation.
  • Delegated review: dispatches a reviewer subagent to provide independent assessment and detect issues early.
  • Actionable outcomes: compiles a structured report with a verdict, critical/important/minor issues, and suggested fixes.

Quick Start

Dispatch a reviewer to assess your latest changes before merging.

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 before merging changes to main?

Automating code review before merging involves dispatching a reviewer subagent to validate code changes and enforce a two-stage workflow. This process applies after completing major features or bug fixes to ensure software quality.

What is a two-stage code review workflow with a self-review checklist?

A two-stage code review workflow first prompts the author to verify conventions, tests, and documentation via a self-review checklist. It then dispatches a delegated reviewer subagent to provide an independent assessment and detect issues early.

How do I get a structured code review report with a final verdict?

To get a structured code review report with a final verdict, dispatch a reviewer subagent to assess your latest changes. It compiles a concise assessment outputting critical, important, and minor issues, strengths, and the final verdict.

Can I use a delegated reviewer subagent for quality assurance after bug fixes?

Yes, you can dispatch a delegated reviewer subagent for quality assurance after bug fixes. It provides an independent assessment of code changes, detecting issues early before merging to main in subagent-driven development.

What's the best way to validate code changes in subagent-driven development?

The best way to validate code changes in subagent-driven development is dispatching a focused reviewer subagent after each task. This enforces structured reviews to catch issues early before merging to main.