requesting-code-review

Reviews git diffs against requirements and produces structured severity-ranked feedback.

1|Updated Feb 10, 2026
One-click install
npx skills add https://github.com/stefanfaur/roach-marketplace --skill requesting-code-review-stefanfaur
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/stefanfaur/roach-marketplace/tree/main/roach/skills/requesting-code-review
Command: npx skills add https://github.com/stefanfaur/roach-marketplace --skill requesting-code-review-stefanfaur

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Verifying that completed work actually meets requirements before merging is error-prone when done informally. This Skill runs a structured code review over a git diff in a forked context, catching bugs, security issues, and requirement gaps before they reach main. ## Core Features & Use Cases - Diff-Based Review: Compares a BASE_SHA to HEAD_SHA range and reviews every significantly modified file in full context, not just the diff hunks. - Severity-Ranked Output: Categorizes findings as Critical, Important, or Minor with file:line references, explanations, and fix guidance. - Requirements Compliance: Reads the referenced plan file and checks the implementation against stated requirements, architecture, testing, and production readiness. - Use Case: After finishing a feature task in subagent-driven development, invoke the skill with the base commit, head commit, a summary of what was implemented, and the plan path to get a clear proceed/no-proceed verdict before merging. ## Quick Start Ask the assistant to request a code review for the changes between your base commit and HEAD, describing what was implemented and pointing to the plan file.

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 recent git changes?▼

Identify the commit just before implementation started as BASE_SHA using git log, get HEAD_SHA with git rev-parse HEAD, then invoke the skill with both SHAs, a description of what was implemented, and the plan or requirements path.

When should I run a code review during development?▼

Run it after each task in subagent-driven development, after completing a major feature, and before merging to main. It is also useful when stuck, before refactoring, or after fixing a complex bug.

What does the code review output include?▼

The review lists strengths, then issues grouped as Critical, Important, and Minor, each with file and line references, why it matters, and how to fix it. It ends with a clear verdict on whether the work is ready to proceed.

Can the reviewer check my code against a plan or requirements document?▼

Yes. If a plan file path is included in the invocation arguments, the reviewer reads that file and checks the diff for requirements compliance alongside code quality, architecture, testing, and production readiness.

What should I do with Critical issues found in a review?▼

Fix Critical issues immediately before proceeding with any further work. Important issues should be fixed before the next task, while Minor issues can be noted for later.