skills.rest
JoeCP17
JoeCP17COMMUNITY
Explore all skills by this author →
WebsiteGitHub

requesting-code-review

Dispatch a code-reviewer subagent with commit SHA ranges for severity-categorized feedback.

8|1|Updated Mar 1, 2026
Search Tags:#git#quality assurance#code review#subagents#merge readiness#dev workflow#production bugs
One-click install
npx skills add https://github.com/JoeCP17/LLM-Dot-files --skill requesting-code-review-joecp17
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/JoeCP17/LLM-Dot-files/tree/main/claude/skills/superpowers/requesting-code-review
Command: npx skills add https://github.com/JoeCP17/LLM-Dot-files --skill requesting-code-review-joecp17

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps prevent bugs and quality regressions by ensuring code changes are reviewed before they move forward in a development workflow.

Core Features & Use Cases

  • Request code review at the right moments: after each subagent task, after major features, and before merging to main.
  • Provide the reviewer with the exact context: commit SHA range plus clear descriptions of what changed and what it was supposed to do.
  • Drive actionable iteration: fix Critical issues immediately, fix Important issues before continuing, and record Minor issues for later.

Quick Start

Ask the assistant to request a code review for your latest changes by preparing BASE_SHA and HEAD_SHA and dispatching the code-reviewer subagent with your implemented summary and plan/requirements.

Frequently Asked Questions about requesting-code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I request a code review before merging changes to main?▼

To request a code review before merging, compute the BASE_SHA and HEAD_SHA for your commit range, then dispatch the code-reviewer subagent with your change descriptions to receive severity-categorized feedback.

When should I run a code review in a subagent-driven dev workflow?▼

You should run a code review in a subagent-driven dev workflow after each subagent task completes, after finishing major features, during refactoring, and as a pre-merge check to catch production bugs early.

What is the best way to verify merge readiness for a git commit range?▼

The best way to verify merge readiness is to run a structured code review pass over your git commit range by dispatching a code-reviewer subagent with the BASE_SHA and HEAD_SHA to identify quality risks.

How do I handle severity-categorized feedback from a code review?▼

To handle severity-categorized feedback from a code review, fix Critical issues immediately, resolve Important issues before continuing your development workflow, and record Minor issues for later.

Can I use this code review process for bug fixes and refactoring?▼

Yes, you can use this code review process for bug fixes, refactoring, and major feature completion by providing the BASE_SHA and HEAD_SHA range with your implemented summary and plan requirements.

What context does the code-reviewer subagent need to produce accurate feedback?▼

The code-reviewer subagent needs the BASE_SHA and HEAD_SHA commit range, plus clear descriptions of what changed and what the changes were supposed to do, to produce severity-categorized feedback.

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
kaivyykaivyy
20

requesting-code-review

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

Community
Intermediate
bobmatnycbobmatnyc
146

Requesting Code Review

Dispatch a code-reviewer subagent to review changes against plans and requirements.

Community
Basic
gajjalaashok75-UIgajjalaashok75-UI
2

requesting-code-review

Review code diffs against requirements and report merge readiness.

Community
Intermediate