requesting-code-review

Dispatches a reviewer subagent to review a git diff against explicit requirements.

17|Updated Feb 19, 2026

Search Tags:#quality assurance #code review #subagent #requirements validation #merge readiness #git diff

Ready to run

npx skills add https://github.com/ivanrvpereira/.agents --skill requesting-code-review-ivanrvpereira

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/ivanrvpereira/.agents/tree/main/skills/requesting-code-review
Command: npx skills add https://github.com/ivanrvpereira/.agents --skill requesting-code-review-ivanrvpereira

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It prevents bugs, requirement drift, and quality issues from compounding by ensuring changes get evaluated against the plan and acceptance criteria before you move on or merge.

Core Features & Use Cases

Dispatch a dedicated code reviewer subagent with tightly scoped context (no reliance on your current session history), focused on assessing the work product.
Review against requirements or a plan by providing a clear description, the exact plan/requirements input, and the git range to inspect.
Severity-based actionability by categorizing findings as Critical, Important, or Minor and providing a concrete recommendation and “ready to merge” verdict.
Use cases: subagent-driven development checkpoints, major feature completion gates, and pre-merge validation.

Quick Start

Request a code review for your latest changes by asking the AI to dispatch the code reviewer subagent and review the git diff between BASE_SHA and HEAD_SHA against your task description and plan.

Frequently Asked Questions about requesting-code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I perform a pre-merge code review against specific requirements?▼

Pre-merge code review against specific requirements is performed by dispatching a reviewer subagent with a scoped context, a git diff range, and your plan to evaluate changes. The review yields severity-based issue classifications and a clear merge readiness verdict.

What is requirement validation in a git diff code review?▼

Requirement validation in a git diff code review is the process of evaluating code changes against explicit acceptance criteria to prevent requirement drift. It categorizes findings by severity and provides evidence-backed feedback before merging.

Can I review code changes without relying on my current session history?▼

You can review code changes without session history by dispatching a dedicated reviewer subagent with tightly scoped context. This subagent evaluates the work product independently using only the provided description, requirements, and git diff range.

How do I get a ready to merge verdict after completing a major feature?▼

To get a ready to merge verdict after completing a major feature, request a code review by providing the task description, plan, and git diff range. The reviewer assesses the changes and returns a concrete recommendation on merge readiness.

What's the best way to classify code review findings by severity?▼

The best way to classify code review findings by severity is to use an automated reviewer subagent that categorizes issues as Critical, Important, or Minor. This ensures actionability and provides evidence-backed feedback for each finding.

When do I need a subagent-driven development checkpoint for code review?▼

You need a subagent-driven development checkpoint for code review when you want to prevent bugs and quality issues from compounding before moving on. It ensures changes get evaluated against the plan and acceptance criteria early.