coderabbit-request

Dispatch CodeRabbit to analyze uncommitted changes and output categorized issues.

Updated Dec 7, 2025
One-click install
npx skills add https://github.com/caiokf/homepage --skill coderabbit-request
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coderabbit-request
Source: https://github.com/caiokf/homepage/tree/main/.claude/skills/coderabbit-request
Command: npx skills add https://github.com/caiokf/homepage --skill coderabbit-request

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill dispatches CodeRabbit reviewer subagent to analyze uncommitted changes and return a structured list of issues. It always requests review before considering work complete.

Core Features & Use Cases

  • Categorizes findings into Critical, Important, and Minor
  • Outputs a JSON structure suitable for downstream triage
  • Encourages a disciplined review-before-complete workflow

Quick Start

Stage changes, run gob add coderabbit --prompt-only --type uncommitted; run gob await-any; parse results into: { "critical": [ { "file": "...", "line": N, "issue": "...", "suggestion": "..." } ], "important": [ ... ], "minor": [ ... ] }

Frequently Asked Questions about coderabbit-request

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

FAQPage Schema
How do I automate code review analysis of my uncommitted changes?

Code review automation dispatches CodeRabbit to analyze uncommitted git changes and categorize findings into critical, important, and minor issues. Stage your changes with git, then use gob to run CodeRabbit with the --prompt-only flag to generate a structured JSON report for triage.

What's the best way to review code changes before marking work complete?

Enforce a disciplined review workflow by analyzing staged changes through CodeRabbit integration. The Skill outputs a priority-ranked JSON structure with critical, important, and minor findings, ensuring issues are caught and documented before work concludes.

Can I use CodeRabbit to review uncommitted changes in JSON and code files?

Yes. CodeRabbit analyzes uncommitted changes across code, configuration, and documentation files. Stage your modifications via git, and the Skill processes them to return structured findings preserving CodeRabbit's exact analysis.

How do I get a structured list of code issues from my staged changes?

Stage changes with git, run the Skill to dispatch CodeRabbit analysis, and receive a JSON object organizing findings by severity: critical, important, and minor, with file, line, issue description, and suggestion fields for each.

What do I need to set up before running automated code review?

Staged git changes are required. The Skill uses gob to invoke CodeRabbit with the --prompt-only flag on uncommitted changes, so your modified files must be staged in git before execution.

Does automated code review work with all file types in my project?

The Skill analyzes any uncommitted file type—code, skills, documentation, and configuration. CodeRabbit processes staged changes across your entire working tree and returns categorized issues in structured JSON format.