requesting-code-review

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

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/LGJ-Jonathan/Jonathan_Global_Claude_Skills --skill requesting-code-review-lgj-jonathan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/LGJ-Jonathan/Jonathan_Global_Claude_Skills/tree/main/superpowers/skills/requesting-code-review
Command: npx skills add https://github.com/LGJ-Jonathan/Jonathan_Global_Claude_Skills --skill requesting-code-review-lgj-jonathan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code changes often get merged without independent review, letting bugs, architecture flaws, and unmet requirements slip into production. This Skill structures the review request process so every task or feature gets evaluated by a dedicated reviewer subagent with precisely crafted context. ## Core Features & Use Cases - Structured Review Dispatch: Fills a code-reviewer template with implementation details, requirements, and git SHAs so the reviewer sees only the work product, not your session history. - Severity-Based Feedback Handling: Categorizes reviewer output into Critical, Important, and Minor issues with clear rules for when to fix, defer, or push back. - Workflow Integration: Defines mandatory review checkpoints for subagent-driven development, plan execution, and pre-merge verification. - Use Case: After completing a feature task, you capture the base and head commit SHAs, dispatch the code-reviewer subagent with the filled template, receive a severity-categorized assessment, fix Critical and Important issues, then proceed to the next task. ## Quick Start Ask the AI to request a code review of your latest 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?

Capture the base and head commit SHAs with git rev-parse, then dispatch a code-reviewer subagent using the provided template. Fill in what was implemented, the requirements, and the commit range so the reviewer evaluates only the diff.

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. Optional reviews help when stuck, before refactoring, or after fixing complex bugs.

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, optimizations). Fix Critical immediately, Important before proceeding, and note Minor for later.

What should I do if the code reviewer is wrong?

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 when the assessment seems incorrect.

Why does the reviewer not see my session history?

The reviewer receives only the filled template with the git diff range and requirements, keeping it focused on the work product rather than your thought process. This also preserves your own context for continued work.