skills.rest
Syedyasir001
Syedyasir001COMMUNITY
Explore all skills by this author →
GitHub

requesting-code-review

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

Updated Apr 17, 2026
Search Tags:#git#workflow#quality assurance#code review#merge#diff#subagent
One-click install
npx skills add https://github.com/Syedyasir001/RVULibPass --skill requesting-code-review-syedyasir001
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/Syedyasir001/RVULibPass/tree/main/.agent/skills/library/requesting-code-review
Command: npx skills add https://github.com/Syedyasir001/RVULibPass --skill requesting-code-review-syedyasir001

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 process by dispatching a dedicated code-reviewer subagent with precisely crafted context, catching issues before they cascade. ## Core Features & Use Cases - Structured Review Dispatch: Provides a repeatable workflow for gathering git SHAs, filling a reviewer template, and dispatching a superpowers:code-reviewer subagent. - Severity-Categorized Feedback: The reviewer template classifies issues as Critical, Important, or Minor with file:line references and a clear merge verdict. - Use Case: After completing a feature task in subagent-driven development, run this Skill to have a fresh reviewer compare your git diff against the plan, then fix Critical and Important issues before moving to the next task. ## Quick Start Ask the assistant to request a code review of the changes between the base 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 to main?▼

Get the base and head commit SHAs with git rev-parse, fill the code-reviewer template with what was implemented and the requirements, then dispatch the superpowers:code-reviewer subagent. Act on 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 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, then categorizes issues by severity.

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

Push back with technical reasoning rather than ignoring the 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. The Skill mandates review after each task and before merges, since small issues compound when left unchecked.

Related Skills

Explore More Software Engineering Skills→
wellcrafted-devwellcrafted-dev
35

spec-execution

Execute specification documents through planned waves of parallel and sequential changes.

Official
Advanced
WesleyMFrederickWesleyMFrederick

requesting-code-review

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

Community
Basic
yusufcmgyusufcmg

springboot-verification

Automate end-to-end verification of Spring Boot projects with builds, tests, and security scans.

Community
Advanced
moduloMomentsmoduloMoments
7

pair

Facilitate pair programming sessions for code review and collaborative file changes.

Official
Intermediate