skills.rest
AarnavBaddam
AarnavBaddamCOMMUNITY
Explore all skills by this author →
GitHub

requesting-code-review

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

Updated Jul 31, 2026
Search Tags:#code quality#git#code review#pull request#merge#diff#subagent
One-click install
npx skills add https://github.com/AarnavBaddam/skills --skill requesting-code-review-aarnavbaddam
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/AarnavBaddam/skills/tree/main/requesting-code-review
Command: npx skills add https://github.com/AarnavBaddam/skills --skill requesting-code-review-aarnavbaddam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code issues caught late compound into larger problems. This Skill provides a structured workflow for requesting code reviews from a dedicated reviewer subagent, ensuring completed work is verified against requirements before merging or moving to the next task. ## Core Features & Use Cases - Subagent-Based Review: Dispatches a general-purpose subagent with a crafted prompt template so the reviewer evaluates only the work product, not your session history. - Structured Review Template: The code-reviewer.md template enforces severity-calibrated feedback (Critical, Important, Minor) with file:line references and a clear merge verdict. - Git Range Targeting: Reviews a precise commit range using BASE_SHA and HEAD_SHA, with read-only review rules that protect the working tree. - Use Case: After finishing a feature task, capture the base and head commit SHAs, dispatch the reviewer subagent with the filled template, then fix Critical and Important issues before proceeding to the next task. ## Quick Start Ask the AI 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 for my changes before merging?▼

Get the base and head commit SHAs with git rev-parse, then dispatch a general-purpose subagent using the code-reviewer.md template filled with your description, requirements, and SHAs. The reviewer returns severity-categorized issues and a merge 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.

Can 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 to inspect history, 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 on the disputed point.

What feedback format does the code review template produce?▼

The reviewer returns Strengths, Issues categorized as Critical, Important, or Minor with file:line references, Recommendations, and an Assessment stating whether the work is ready to merge with reasoning.

Related Skills

Explore More Software Engineering Skills→
Strategic-AutomationStrategic-Automation
6

requesting-code-review

Automate pre-commit verification with security scans, quality gates, and reviewer subagent.

Official
Advanced
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
garden-cogarden-co
154

spec

Plan feature work with design artifacts and explicit approval gates.

Official
Advanced