skills.rest
ttnhan18062000
ttnhan18062000COMMUNITY
Explore all skills by this author →
GitHub

requesting-code-review

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

Updated Feb 8, 2026
Search Tags:#workflow#quality assurance#code review#feedback#subagent#git diff#pre-merge
One-click install
npx skills add https://github.com/ttnhan18062000/rpg-based-simulation --skill requesting-code-review-ttnhan18062000
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/ttnhan18062000/rpg-based-simulation/tree/main/docs/archive/legacy_agents_skills_20260722/requesting-code-review
Command: npx skills add https://github.com/ttnhan18062000/rpg-based-simulation --skill requesting-code-review-ttnhan18062000

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It catches code quality, architecture, and requirement gaps early by dispatching an independent reviewer subagent with a precisely crafted context, preventing issues from cascading across tasks or reaching main. ## Core Features & Use Cases - Structured Review Dispatch: Builds a reviewer prompt from a template with placeholders for what was implemented, requirements, and git SHAs. - Severity-Categorized Feedback: Returns issues classified as Critical, Important, or Minor with file:line references and a merge readiness verdict. - Use Case: After finishing a feature task, you capture BASE_SHA and HEAD_SHA, dispatch the code-reviewer subagent with the filled template, receive categorized feedback, fix Critical and Important issues, and then proceed to the next task or merge. ## Quick Start Ask the AI 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?▼

Capture the base and head git SHAs, then dispatch a code-reviewer subagent using the provided template with what was implemented, the requirements, and the SHA range. Act on the returned feedback by fixing Critical and Important issues before merging.

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.

What does the code reviewer check in a review?▼

The reviewer checks code quality, architecture, testing, and requirement coverage against the plan. It categorizes issues as Critical, Important, or Minor with file:line references and gives a clear merge readiness verdict.

What should I do if I disagree with the reviewer's feedback?▼

Push back with technical reasoning, showing code or tests that prove the implementation works, and request clarification. Never ignore valid Critical issues, but valid technical disagreement is supported.

Why does the reviewer not receive my session history?▼

The reviewer gets only precisely crafted context about the work product, not your thought process. This keeps the review focused on the code itself and preserves your own context for continued work.

Related Skills

Explore More Software Engineering Skills→
greglambgreglamb
1

test-driven-development

Enforces test-first development by writing failing tests before production code.

Community
Intermediate
WesleyMFrederickWesleyMFrederick

requesting-code-review

Dispatch a code-reviewer subagent to review Git changes between BASE_SHA and HEAD_SHA.

Community
Basic
phraphra

code-review

Review modified code files and auto-fix mechanical issues.

Community
Advanced
ccomkhjccomkhj
8

pair-coding

Coordinate Claude Code and Codex pair-programming with proposer/reviewer sign-offs.

Community
Advanced