skills.rest
johnstegeman
johnstegemanCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

requesting-code-review

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

Updated Jul 22, 2026
Search Tags:#workflow#quality assurance#code review#merge#subagent#git diff
One-click install
npx skills add https://github.com/johnstegeman/pi-packages --skill requesting-code-review-johnstegeman
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/johnstegeman/pi-packages/tree/main/packages/pi-superpowers-plus/skills/requesting-code-review
Command: npx skills add https://github.com/johnstegeman/pi-packages --skill requesting-code-review-johnstegeman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Completed code often ships without independent review, letting defects cascade into later work. This Skill structures the review request so a dedicated reviewer subagent evaluates a precise git range against the original requirements, keeping the coordinator's context window free. ## Core Features & Use Cases - Subagent-Based Review: Dispatches a code-reviewer subagent with a crafted prompt template covering description, requirements, and git SHAs, so the diff is evaluated in the reviewer's context rather than yours. - Structured Feedback Triage: Returns findings classified as Critical, Important, and Minor issues with an overall assessment, plus guidance on when to fix, defer, or push back. - Use Case: After finishing a feature branch, compute BASE_SHA with git merge-base and HEAD_SHA with git rev-parse, dispatch the reviewer using the code-reviewer.md template, and address Important issues before merging to main. ## Quick Start Ask the agent to request a code review of the current branch against main before merging.

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 for a git branch?▼

Compute BASE_SHA with git merge-base against the base branch and HEAD_SHA with git rev-parse HEAD, then dispatch a code-reviewer subagent using the provided template with a description, requirements, and both SHAs. The reviewer returns strengths, issues, and an assessment.

When should I request a code review during development?▼

Request review after completing a major feature and before merging to main. It is also valuable when stuck, before refactoring for a baseline check, or after fixing a complex bug.

Why use a reviewer subagent instead of reviewing the diff myself?▼

Reviewing the diff inline consumes the coordinator's context window. A subagent evaluates the diff in its own context and returns only the findings, keeping the main session focused on driving the work.

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

Push back with technical reasoning, showing code or tests that prove the implementation works, and request clarification. Do not ignore valid feedback, but valid disagreement with evidence is supported.

Can the reviewer subagent modify my working tree?▼

No. The review is read-only on the checkout. The reviewer uses git show, git diff, and git log, and must use a separate temporary worktree if it needs another revision checked out.

Related Skills

Explore More Software Engineering Skills→
MoofonLiMoofonLi
2

requesting-code-review

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

Community
Intermediate
SeanHoggSeanHogg
3

prepare-pr

Rebase a GitHub Pull Request onto main, fix review findings, run gates, and push.

Community
Advanced
phraphra

code-review

Review modified code files and auto-fix mechanical issues.

Community
Advanced
NooBatNooBat

review-pr

Automate GitHub pull request reviews with inline comments.

Community
Intermediate