requesting-code-review

Dispatch a code-reviewer subagent to assess new changes with structured inputs.

19|4|Updated Feb 1, 2026

Search Tags:#automation #feedback #subagent #code-review #pull-request #dev-workflow

Ready to run

npx skills add https://github.com/jarredkenny/agency-ai --skill requesting-code-review-jarredkenny

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/jarredkenny/agency-ai/tree/main/roles/orchestrator/skills/requesting-code-review
Command: npx skills add https://github.com/jarredkenny/agency-ai --skill requesting-code-review-jarredkenny

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the early-quality review by dispatching a code-reviewer subagent to assess new changes and surface issues before they cascade.

Core Features & Use Cases

Automated code review trigger: Automatically request a review after each task, after major features, or before merging to main.
Structured feedback workflow: Guides reviewers with clear placeholders and expectations, enabling fast, actionable feedback.
Integrates with developer workflows: Fits into subagent-driven development and task planning for iterative quality checks.

Quick Start

After completing a task, dispatch the code-reviewer subagent to evaluate your changes and provide structured feedback. Then populate the review fields with WHAT_WAS_IMPLEMENTED, PLAN_OR_REQUIREMENTS, BASE_SHA, HEAD_SHA, and DESCRIPTION to proceed.

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?▼

Automate code reviews by dispatching a code-reviewer subagent to assess changes after each task or major feature. This skill triggers structured feedback early by evaluating new changes against your requirements before merging to main.

What inputs are required to request an automated pull request review?▼

Requesting a pull request review requires WHAT_WAS_IMPLEMENTED, PLAN_OR_REQUIREMENTS, BASE_SHA, HEAD_SHA, and DESCRIPTION inputs. These fields drive the code-reviewer subagent tasks to capture structured, actionable feedback.

When should I trigger peer code review in a subagent-driven development workflow?▼

Trigger peer code review in subagent-driven development after completing each task, finishing major features, or before merging to main. Early-quality review surfaces issues before they cascade into larger problems.

Does subagent-driven code review work without external dependencies?▼

Subagent-driven code review works without external dependencies, relying entirely on the superpowers:code-reviewer subagent. It fits directly into existing developer workflows and task planning for iterative quality checks.

How does structured feedback improve automated code review?▼

Structured feedback improves automated code review by guiding reviewers with clear placeholders and expectations. This approach enables fast, actionable feedback by mapping changes directly against plan requirements and descriptions.

Can I use this code review automation for iterative quality checks during feature development?▼

You can use this code review automation for iterative quality checks during feature development. It integrates into subagent-driven development workflows to evaluate changes after each task, ensuring issues are caught early.