requesting-code-review

Name: requesting-code-review
Availability: InStock
Author: sammy9322

Dispatch a code reviewer subagent to evaluate changes against project requirements.

Updated Apr 18, 2026

Search Tags:#git #quality assurance #code review #development workflow #subagent #bug detection #pre-merge validation

Ready to run

npx skills add https://github.com/sammy9322/ventura-dental-facturacion --skill requesting-code-review-sammy9322

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of undetected code defects, requirement misalignment, and technical debt that accumulate during development and cause costly rework, failed merges, or production issues if caught too late.

Core Features & Use Cases

Structured Code Review Dispatch: Quickly send a dedicated code reviewer subagent with precise context of your changes, no need to manually share session history or vague change summaries.
Severity-Categorized Feedback: Get consistent, actionable review results split into Critical, Important, and Minor issues, aligned with your original project requirements and code quality standards.
Flexible Workflow Integration: Use after each task in subagent-driven development, before merging to main, after completing major features, or when stuck on a complex bug to get an unbiased assessment of your work.

Quick Start

Use the requesting-code-review skill to dispatch a code reviewer subagent to evaluate your latest code changes against the project requirements and identify any issues before proceeding.

Frequently Asked Questions about requesting-code-review

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

FAQPage Schema

How do I get a structured code review before merging changes to main?▼

To get a structured code review before merging, dispatch a dedicated reviewer subagent that evaluates your changes against original plans and quality standards. This provides severity-categorized feedback on critical, important, and minor issues without consuming your active development context.

What is subagent-driven code review and how does it work?▼

Subagent-driven code review sends a dedicated reviewer with precise change context to evaluate code against project requirements. It works by providing structured, context-focused assessments that identify defects and requirement misalignment without requiring manual session history sharing.

When should I request a peer code review during my development workflow?▼

You should request a peer code review after each task in subagent-driven development, before merging to main, after completing major features, or when stuck on a complex bug. This catches undetected defects and technical debt early, preventing costly rework or failed merges.

Does pre-merge validation work with subagent-driven feature implementation?▼

Yes, pre-merge validation works with subagent-driven feature implementation by dispatching a reviewer subagent to evaluate your latest changes. It assesses production readiness and code quality standards, ensuring your feature implementation aligns with original project requirements before integration.

What's the best way to catch code defects and requirement misalignment early?▼

The best way to catch code defects and requirement misalignment early is through targeted peer reviews using a dedicated subagent. This approach provides unbiased assessments of your work, evaluating changes against original plans and quality standards to prevent costly rework.

Can I use automated code review for complex bug fixes without losing my active context?▼

Yes, you can use automated code review for complex bug fixes without losing your active context. The reviewer subagent operates independently with precise change context, delivering severity-categorized feedback on critical, important, and minor issues while preserving your working session.