skills.rest
TumeloRamaphosa
TumeloRamaphosaCOMMUNITY
Explore all skills by this author →
GitHub

requesting-code-review

Request automated code review for a git change range before merging.

Updated May 7, 2026
Search Tags:#quality assurance#code review#merge readiness#git diff#severity triage#subagent workflow#architecture feedback
One-click install
npx skills add https://github.com/TumeloRamaphosa/StudEx-Valley-OS --skill requesting-code-review-tumeloramaphosa
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/TumeloRamaphosa/StudEx-Valley-OS/tree/main/.claude/skills/superpowers/skills/requesting-code-review
Command: npx skills add https://github.com/TumeloRamaphosa/StudEx-Valley-OS --skill requesting-code-review-tumeloramaphosa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It reduces the risk of shipping broken or noncompliant changes by getting an independent code reviewer subagent to evaluate your work before it cascades into more tasks or merges.

Core Features & Use Cases

  • Trigger review at key workflow moments: after each task in subagent-driven development, after major features, and before merging to main.
  • Provide tightly scoped context: reviewer receives a crafted prompt and a git SHA range (base to head) rather than your full session history.
  • Actionable feedback triage: handle Critical issues immediately, Important issues before continuing, and treat Minor issues as backlog.

Quick Start

Use requesting-code-review to have a code reviewer subagent evaluate the changes between your {BASE_SHA} and {HEAD_SHA} against {PLAN_OR_REQUIREMENTS} right before you merge.

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 a code review for a specific git diff range before merging?▼

To automate code review for a git diff, provide a base SHA, head SHA, and plan requirements to dispatch a reviewer subagent that evaluates merge readiness and issues severity-based remediation guidance.

What is the best way to check merge readiness in a subagent-driven development workflow?▼

Checking merge readiness in a subagent workflow involves triggering an independent reviewer subagent at major feature checkpoints to evaluate changes against your plan and prevent defects from reaching main.

Can I scope an automated code review to only my recent git changes instead of the full session history?▼

Yes, you can scope an automated code review by providing a crafted reviewer dispatch with a specific base SHA and head SHA range, ensuring the subagent only evaluates the targeted git diff.

How does severity triage work for code review feedback?▼

Severity triage in code review feedback categorizes issues into Critical, Important, and Minor, requiring immediate fixes for Critical, resolution for Important before continuing, and backlog treatment for Minor.

When do I need to request a pre-merge validation code review?▼

You need to request pre-merge validation code review right before merging to main, after completing individual tasks in subagent-driven development, or after finishing major features to catch architecture and compliance issues early.

Does automated code review work without integrating external quality assurance dependencies?▼

Yes, automated code review works without external quality assurance dependencies by using a standalone subagent workflow that evaluates your provided git SHA range and plan requirements to generate actionable feedback.

Related Skills

Explore More Software Engineering Skills→
WesleyMFrederickWesleyMFrederick

requesting-code-review

Dispatch a code-reviewer subagent to review Git changes between BASE_SHA and HEAD_SHA.

Community
Basic
kaivyykaivyy
20

requesting-code-review

Dispatch a subagent to analyze git diffs and categorize issues by severity.

Community
Intermediate
droxeydroxey
1

requesting-code-review

Dispatch a code reviewer subagent to evaluate SHA-scoped code changes.

Community
Intermediate
VYRE-StudiosVYRE-Studios

code-review

Review Git changes for correctness, security, performance, and maintainability.

Official
Advanced