requesting-code-review

Dispatch a code reviewer subagent to evaluate git diffs against requirements.

Updated Jan 2, 2025
One-click install
npx skills add https://github.com/mcinnisd/gymbro --skill requesting-code-review-mcinnisd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/mcinnisd/gymbro/tree/main/.agents/skills/requesting-code-review
Command: npx skills add https://github.com/mcinnisd/gymbro --skill requesting-code-review-mcinnisd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Completed code changes often go unreviewed or get shallow self-review, letting bugs and architectural issues cascade into later work. This Skill structures the process of dispatching an independent code reviewer subagent with precisely crafted context before merging or proceeding. ## Core Features & Use Cases - Structured Review Dispatch: Provides a repeatable workflow for capturing git SHAs and dispatching a general-purpose reviewer subagent with a fill-in template. - Severity-Calibrated Feedback: The reviewer template enforces categorized output (Critical, Important, Minor) with file:line references and a clear merge verdict. - Read-Only Review Safety: Instructs the reviewer to never mutate the working tree, HEAD, or branch state during inspection. - Use Case: After finishing a feature task, you run git rev-parse to get the base and head SHAs, dispatch the reviewer with the template, receive categorized issues, fix the Important ones, and only then continue to the next task. ## Quick Start Ask the AI to request a code review of your latest commits using the requesting-code-review skill 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 with a subagent?

Get the base and head commit SHAs with git rev-parse, then dispatch a general-purpose subagent using the code-reviewer.md template. Fill in the description, requirements, and SHA placeholders, then act on the returned severity-categorized feedback.

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, and must use a separate temporary worktree if it needs another revision, never moving HEAD.

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 disputed point.

What output format does the code review produce?

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