requesting-code-review

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

2|Updated Aug 15, 2025
One-click install
npx skills add https://github.com/Grupo-6-ADS-B/FittNutri --skill requesting-code-review-grupo-6-ads-b
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/Grupo-6-ADS-B/FittNutri/tree/main/.claude/skills/requesting-code-review
Command: npx skills add https://github.com/Grupo-6-ADS-B/FittNutri --skill requesting-code-review-grupo-6-ads-b

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code changes often get merged without structured review, letting bugs, architectural flaws, and unmet requirements slip into production. This Skill standardizes the review process by dispatching a dedicated code-reviewer subagent with precisely crafted context, catching issues early before they cascade. ## Core Features & Use Cases - Structured Review Dispatch: Provides a repeatable workflow for gathering git SHAs and dispatching a code-reviewer subagent with a fill-in template covering implementation, requirements, and commit range. - Severity-Categorized Feedback: The reviewer template classifies issues as Critical, Important, or Minor with file:line references, and delivers a clear merge-readiness verdict. - Workflow Integration: Defines when to request reviews—after each task in subagent-driven development, after major features, and before merging to main. - Use Case: After completing a feature task, you capture the base and head commit SHAs, dispatch the reviewer with the plan reference, receive categorized feedback, fix Critical and Important issues, and only then proceed to the next task. ## Quick Start Ask the assistant to request a code review of the changes you just implemented before merging them 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 before merging to main?

Capture the base and head commit SHAs with git rev-parse, then dispatch the code-reviewer subagent using the provided template with what was implemented, the plan reference, and the commit range. Act on Critical and Important issues before merging.

When should I request a code review during development?

Request reviews after each task in subagent-driven development, after completing major features, and before merging to main. Reviews are 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 coverage, and requirement compliance across the specified commit range. It categorizes findings as Critical, Important, or Minor with file:line references and gives a merge-readiness verdict.

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 reviewer's concern.

Can I skip code review for simple changes?

No, skipping review because a change seems simple is explicitly flagged as a red flag. The workflow requires reviewing early and often, since even small changes can introduce issues that compound across tasks.