skills.rest
AllBeingsFuture
AllBeingsFutureCOMMUNITY
Explore all skills by this author →
GitHub

obra/superpowers@requesting-code-review

Dispatch a code-reviewer subagent to validate tasks after each step.

9|2|Updated Mar 18, 2026
Search Tags:#automation#git#workflow#templates#subagent#developer-tools#code-review
One-click install
npx skills add https://github.com/AllBeingsFuture/AllBeingsFuture --skill obra-superpowers-requesting-code-review-allbeingsfuture
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: obra/superpowers@requesting-code-review
Source: https://github.com/AllBeingsFuture/AllBeingsFuture/tree/main/electron/embedded-assets/skills/superpowers-requesting-review
Command: npx skills add https://github.com/AllBeingsFuture/AllBeingsFuture --skill obra-superpowers-requesting-code-review-allbeingsfuture

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Dispatch early code-quality control by automatically dispatching a code-review subagent to identify issues before they cascade.

Core Features & Use Cases

  • Automatically trigger a code-reviewer subagent after each task in subagent-driven development to keep changes aligned with requirements.
  • Enforce early feedback before major feature completion and prior to merging to main to reduce regressions.
  • Provides structured review prompts and templates to standardize feedback and improve collaboration.

Quick Start

Dispatch the code-reviewer subagent after each task and provide BASE_SHA and HEAD_SHA as references.

Frequently Asked Questions about obra/superpowers@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 to main?▼

You can automate code review before merging to main by dispatching a code-reviewer subagent. This skill triggers early feedback after major features to identify issues and reduce regressions.

What is subagent-driven development workflow?▼

Subagent-driven development workflow validates tasks after each step by automatically dispatching a code-reviewer subagent. It uses structured templates to coordinate reviews and keep changes aligned with requirements.

How do I trigger a code-reviewer subagent after a git commit?▼

Trigger a code-reviewer subagent after a git commit by providing BASE_SHA and HEAD_SHA as references. This supplies the structured prompts needed to execute the Task-driven review workflow.

Do I need specific templates to standardize code review feedback?▼

Yes, this workflow relies on structured templates and prompts like WHAT_WAS_IMPLEMENTED to standardize code review feedback. These templates coordinate the subagent dispatch process and improve collaboration.

Can I use this automated code review for every task in my workflow?▼

Yes, you can dispatch the code-reviewer subagent after each task in your workflow. Applying it continuously during subagent-driven development enforces early quality control before issues cascade.

Why should I use subagents for early code-quality control instead of manual review?▼

Using subagents for early code-quality control automatically catches issues before they cascade. It enforces structured feedback prior to merging to main, reducing regressions better than manual review.

Related Skills

Explore More Software Engineering Skills→
alffeialffei
69

requesting-code-review

Dispatch a code-reviewer subagent to validate git changes before merging.

Community
Intermediate
ed3daied3dai
5

requesting-code-review

Dispatch a code-reviewer subagent after task completion for structured review loops.

Official
Intermediate
emptistemptist

create-subagents

Create and manage Claude Code subagents and Task tool workflows.

Community
Advanced
nicolanoviellnicolanoviell
2

code-review

Review code changes for bugs, style issues, and best practices.

Community
Intermediate