requesting-code-review

Dispatches a code reviewer subagent to evaluate git changes against requirements before merging.

1|Updated Jul 6, 2015
One-click install
npx skills add https://github.com/ksolomon/dotfiles --skill requesting-code-review-ksolomon
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/ksolomon/dotfiles/tree/main/AI/.claude/plugins/cache/claude-plugins-official/superpowers/6.1.1/skills/requesting-code-review
Command: npx skills add https://github.com/ksolomon/dotfiles --skill requesting-code-review-ksolomon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code issues caught late compound into larger problems, and self-review often misses defects in your own work. This Skill provides a structured workflow for dispatching an independent code reviewer subagent with precisely crafted context, catching Critical and Important issues before they cascade into more work. ## Core Features & Use Cases - Subagent-Based Review: Dispatches a general-purpose subagent with a ready-made reviewer prompt template, keeping the reviewer focused on the work product rather than your session history. - Structured Feedback Format: Returns categorized findings (Critical, Important, Minor) with file:line references, plus strengths, recommendations, and a clear merge verdict. - Git Range Review: Reviews a specific commit range using BASE_SHA and HEAD_SHA, with read-only rules that prevent the reviewer from mutating your working tree. - Use Case: After completing a task in subagent-driven development, you run the review workflow before starting the next task. The reviewer flags a missing progress indicator as Important, you fix it immediately, and proceed with confidence. ## Quick Start Ask the AI to request a code review of your recent commits using the code-reviewer template before merging to main.

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

Get the base and head commit SHAs with git rev-parse, then dispatch a general-purpose subagent using the code-reviewer.md template. Fill in the description, requirements, and SHA placeholders, and the reviewer returns categorized issues with a merge verdict.

When should I request a code review during development?▼

Request review after each task in subagent-driven development, after completing major features, and before merging to main. It is also valuable when stuck, before refactoring as a baseline check, or after fixing a complex bug.

Can the code reviewer subagent modify my working tree?▼

No, the review is strictly read-only on your checkout. The reviewer uses git show, git diff, and git log to inspect history, and must use a separate git worktree in a temporary directory if it needs a different revision.

What should I do if the code reviewer is wrong about an issue?▼

Push back with technical reasoning rather than accepting invalid feedback. Show code or tests that prove the implementation works, and request clarification from the reviewer on the specific concern.

How are code review issues categorized by severity?▼

Issues are split into Critical (bugs, security, data loss), Important (architecture problems, missing features, test gaps), and Minor (style, polish). Fix Critical issues immediately and Important issues before proceeding; note Minor issues for later.