requesting-code-review

Dispatches a subagent to review git diffs and categorize severity of code issues.

Updated Jun 2, 2026
One-click install
npx skills add https://github.com/qiushibang/skill-creator-pro --skill requesting-code-review-qiushibang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/qiushibang/skill-creator-pro/tree/main/references/superpowers/requesting-code-review
Command: npx skills add https://github.com/qiushibang/skill-creator-pro --skill requesting-code-review-qiushibang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of undetected code issues, architecture flaws, and security vulnerabilities cascading into later development stages, where they become far more expensive and time-consuming to fix, by enforcing consistent, focused code reviews at critical checkpoints.

Core Features & Use Cases

  • Structured Review Workflow: Enforces mandatory review checkpoints after each subagent-driven development task, after completing major features, and before merging to main, plus optional valuable checkpoints when stuck, before refactoring, or after fixing complex bugs.
  • Focused Reviewer Context: Dispatches a dedicated code reviewer subagent with only the precise context needed for evaluation (implementation description, requirements, git diff range) to avoid noise from session history and keep feedback targeted at the work product.
  • Categorized Actionable Feedback: Uses a standardized review template that categorizes issues by severity (Critical, Important, Minor), provides specific file:line references, explains the impact of each issue, and includes a clear merge readiness assessment.
  • Use Case: For example, after completing a new payment processing feature, use this Skill to get a targeted review of the changes against the original requirements, catch missing error handling or security gaps, and get a clear verdict on merge readiness before pushing to main.

Quick Start

Use the requesting-code-review skill to review the code changes you just completed for the inventory sync feature against the requirements in docs/plans/inventory-sync.md before merging to the main branch.

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 a pull request?

Automating code review before merging a pull request requires dispatching a dedicated subagent to evaluate your git diff. This skill provides pre-merge validation by analyzing changes against requirements, categorizing issues by severity, and outputting a clear merge readiness assessment.

What is the best way to catch security vulnerabilities and architecture flaws early in development?

Catching security vulnerabilities and architecture flaws early involves enforcing structured review checkpoints after completing major features. This skill dispatches a focused reviewer subagent with precise context to identify costly downstream issues before they cascade into the main branch.

How do I perform a code review on a specific git commit range?

Performing a code review on a specific git commit range requires providing the base and head SHAs to define the scope. The skill uses these git references to dispatch a subagent that evaluates the diff and outputs categorized, actionable fix recommendations.

Can I use a subagent to review code changes without including session history noise?

Using a subagent to review code changes without session history noise is exactly what this skill does. It dispatches a general-purpose subagent with a structured prompt containing only the implementation description, requirements, and git diff range to keep feedback targeted.

When should I run a pre-merge validation check on my feature branch?

Running a pre-merge validation check is essential after completing major features, finishing subagent-driven development tasks, or before pushing to main. The skill enforces these mandatory checkpoints to ensure code quality and prevent undetected issues from reaching production.

Does automated code review provide actionable feedback for fixing detected bugs?

Automated code review provides actionable feedback by using a standardized template that categorizes issues by severity. It includes specific file and line references, explains the impact of each detected bug, and delivers a clear verdict on whether the code is ready to merge.