skills.rest
johsquaree
johsquareeCOMMUNITY
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 30, 2026
Search Tags:#code quality#code review#subagent#git diff#pre-merge#review template
One-click install
npx skills add https://github.com/johsquaree/claude-basic-docs --skill requesting-code-review-johsquaree
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/johsquaree/claude-basic-docs/tree/main/.claude/skills/requesting-code-review
Command: npx skills add https://github.com/johsquaree/claude-basic-docs --skill requesting-code-review-johsquaree

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When completing tasks or features, self-reviewing your own code burns context and misses issues. This Skill dispatches a dedicated code reviewer subagent with precisely crafted context so problems are caught before they cascade into more work. ## Core Features & Use Cases - Structured Review Dispatch: Fills a reusable reviewer prompt template with a description, requirements, and git SHA range, then sends it to a general-purpose subagent. - Severity-Calibrated Feedback: The reviewer returns strengths, issues categorized as Critical, Important, or Minor, recommendations, and a clear merge verdict. - Read-Only Review Safety: The reviewer is instructed to inspect history with git diff and git show without mutating the working tree or HEAD. - Use Case: After finishing a task in subagent-driven development, capture the base and head SHAs, dispatch the reviewer, fix Critical and Important issues, then proceed to the next task or merge. ## Quick Start Ask the assistant to request a code review of the changes between the previous commit and HEAD using the code-reviewer template 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 before merging changes?▼

Get the base and head commit SHAs with git rev-parse, fill the code-reviewer template with a description, requirements, and the SHA range, then dispatch a general-purpose subagent. It returns categorized issues and a merge readiness verdict.

When should I request a code review during development?▼

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

Does the code reviewer subagent modify my working tree?▼

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

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

Push back with technical reasoning rather than accepting incorrect feedback. Show code or tests that prove the implementation works, and request clarification from the reviewer when needed.

How are code review issues categorized by severity?▼

Issues are grouped into Critical (bugs, security, data loss), Important (architecture problems, missing features, test gaps), and Minor (style, polish). Fix Critical immediately and Important before proceeding.

Related Skills

Explore More Software Engineering Skills→
russosalvrussosalv
5

requesting-code-review

Dispatch a code-reviewer subagent for git-range reviews with severity checklists.

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
RisorseArtificialiRisorseArtificiali
9

adversarial-code-review

Reviews branches and pull requests using fresh-context reviewer subagents with execution-based verification.

Official
Advanced