requesting-code-review

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

Dispatch a reviewer subagent to categorize code defects by severity.

26|1|Updated Mar 19, 2026

Search Tags:#code quality #git #code review #development workflow #subagent #merge checks

Ready to run

npx skills add https://github.com/BinyaminEden/claude-combine --skill requesting-code-review-binyamineden

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of merging unvetted code that contains bugs, requirement mismatches, or architectural flaws, which would otherwise require costly rework after deployment and slow down development cycles.

Core Features & Use Cases

Dedicated Reviewer Subagent Dispatch: Sends a focused general-purpose subagent with precise context of your changes, requirements, and git range to avoid bias from your session history.
Structured Severity-Categorized Feedback: Enforces a standard review output that separates Critical, Important, and Minor issues, plus a clear merge readiness assessment.
Workflow Integration: Works with subagent-driven development, plan execution, and ad-hoc development workflows, with mandatory review checkpoints after task completion, before refactoring, and prior to merging.

Quick Start

Use the requesting-code-review skill to review the changes in your latest commit against the requirements in docs/feature-plan.md 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 catch code defects and architectural flaws before merging to main?▼

To catch code defects before merging to main, you can use an automated code review process that dispatches a dedicated subagent with your git base and head SHAs, requirements document, and work summary to generate structured, severity-categorized feedback.

What is a structured code review and how does it categorize feedback?▼

A structured code review categorizes feedback by severity, separating Critical, Important, and Minor issues to provide a clear merge readiness assessment. This approach prevents unvetted code with bugs or requirement mismatches from cascading into production.

Can I use an automated code review with subagent-driven development workflows?▼

Yes, automated code review works with subagent-driven development, plan execution, and ad-hoc feature workflows. It serves as a mandatory review checkpoint after task completion, before refactoring, and prior to merging to your main branch.

What do I need to provide to review code changes against a feature plan?▼

To review code changes against a feature plan, you need to provide the git base and head SHAs for the change range, a summary of the implemented work, and the associated plan or requirements document to generate accurate, structured feedback.

Why dispatch a separate subagent for peer code review instead of reviewing in my current session?▼

Dispatching a separate subagent for peer code review provides focused context of your changes and requirements while avoiding bias from your session history. This isolated approach enforces a standard review output with clear merge readiness assessment.

When should I run a code review check during my development workflow?▼

You should run a code review check after task completion, before refactoring, and prior to merging to main. These mandatory checkpoints catch requirement deviations and architectural flaws early, eliminating costly rework after deployment.