requesting-code-review

Review git code changes for production readiness and severity-ranked issues.

264|11|Updated Apr 25, 2026

Search Tags:#git #quality assurance #code review #production readiness #subagent #merge verification

Ready to run

npx skills add https://github.com/coco-research/coco --skill requesting-code-review-coco-research

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you verify completed work before it ships, reducing the risk of hidden bugs, missed requirements, and avoidable rework.

Core Features & Use Cases

Early Review Timing: Use it after a task, after a major feature, before a merge, or whenever you need a second set of eyes.
Focused Reviewer Context: It instructs a code-reviewer subagent to assess only the implementation and the specified git range, not your full session history.
Actionable Triage: It organizes feedback into strengths, critical issues, important issues, and minor suggestions so you can fix the right things first.

Quick Start

Ask this Skill to review your latest implementation against the plan, using the relevant base and head commits, and return a severity-ranked assessment with clear next steps.

Frequently Asked Questions about requesting-code-review

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

FAQPage Schema

How do I verify code changes for production readiness before a git merge?▼

To verify production readiness before a merge, you review completed code changes by providing the base and head git SHAs. This triggers a focused assessment of the implementation context to catch defects and prevent hidden bugs from shipping.

What is the best way to review subagent-driven development output before merging?▼

Reviewing subagent-driven development output requires providing the base and head git commits to a code-reviewer subagent. This constrains the review to only the specified git range and implementation, ignoring full session history.

How do I triage code review issues by severity when checking completed work?▼

Triage code review issues by organizing feedback into strengths, critical issues, important issues, and minor suggestions. This severity-based triage provides a clear readiness verdict and actionable recommendations so you can fix the right things first.

When should I run a pre-merge code review on my feature branch?▼

Run a pre-merge code review after a task, major feature completion, refactoring, or bug fix. Checking these completed code changes against the plan before merging reduces the risk of missed requirements and avoidable rework.

Do I need specific git commit references to run a code review on my changes?▼

Yes, you need the base and head git SHAs to run this code review. These commit references define the exact implementation diff for the code-reviewer subagent to assess production readiness.

Can I review my entire session history instead of a specific git range?▼

No, this code review process focuses strictly on the specified git range and implementation context. It does not assess your full session history, ensuring the review remains targeted on the actual code changes.