skills.rest
chhpt
chhptCOMMUNITY
Explore all skills by this author →
GitHub

requesting-code-review

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

Updated Aug 23, 2026
Search Tags:#code quality#code review#development workflow#subagent#git diff#merge verification
One-click install
npx skills add https://github.com/chhpt/skills --skill requesting-code-review-chhpt
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/chhpt/skills/tree/main/skills/requesting-code-review
Command: npx skills add https://github.com/chhpt/skills --skill requesting-code-review-chhpt

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 a fresh reviewer subagent evaluates your work against the original plan with precisely crafted context. ## Core Features & Use Cases - Structured Review Dispatch: Fills a code-reviewer template with what was implemented, the plan, and git SHAs so the reviewer sees only the work product. - Severity-Based Feedback: Returns issues categorized as Critical, Important, or Minor with file:line references and a clear merge verdict. - Use Case: After finishing a feature task, you capture BASE_SHA and HEAD_SHA, dispatch the reviewer subagent, receive feedback flagging a missing progress indicator, fix it, and proceed to the next task with confidence. ## Quick Start Ask the assistant to request a code review of the changes between the previous commit and HEAD using the code-reviewer template.

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

Capture the base and head git SHAs, then dispatch a code-reviewer subagent using the provided template with what was implemented, the plan, and the commit range. The reviewer 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 major features, and before merging to main. It is also valuable when stuck, before refactoring, or after fixing a complex bug.

What does the code reviewer check in a git diff?▼

The reviewer checks code quality, architecture, testing, and requirement coverage against the plan. It also assesses production readiness including migrations, backward compatibility, and documentation.

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

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

Can I skip code review for simple changes?▼

No, skipping review because a change seems simple is listed as a red flag. Critical issues must be fixed immediately and Important issues resolved before proceeding, regardless of perceived simplicity.

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
gquthiergquthier
14

requesting-code-review

Dispatch a reviewer subagent to validate code changes before merging.

Community
Advanced
jeremyaryjeremyary
7

status

Run linting, type checks, tests, and dependency audits with pass/fail reporting.

Community
Intermediate
in-the-loop-labsin-the-loop-labs
48

pr

Open the current branch's GitHub pull request in the pair-review web UI.

Official
Basic