coderabbit-review

Waits for, triages, and settles CodeRabbit pull-request reviews via GitHub checks and GraphQL threads.

Updated Nov 2, 2025
One-click install
npx skills add https://github.com/fx/skills --skill coderabbit-review-fx
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: coderabbit-review
Source: https://github.com/fx/skills/tree/main/skills/coderabbit-review
Command: npx skills add https://github.com/fx/skills --skill coderabbit-review-fx

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? CodeRabbit's GitHub App reviews pull requests automatically, but its findings arrive as check conclusions and review threads that must be waited on, triaged against a Scope Brief, and settled before merge — a process that is easy to get wrong by polling blindly, misreading pending states, or leaving unresolved threads behind a merge gate. ## Core Features & Use Cases - Status-protocol waiter script: Polls the CodeRabbit check with a wall-clock budget and emits a machine-readable STATUS line (TERMINAL_PASS, TERMINAL_FAIL, PENDING, NOT_CONFIGURED, ERROR) so callers branch on facts, not prose. - Scope Brief triage: Fetches all CodeRabbit review threads via paginated GraphQL and classifies each as blocking, immaterial, or deferred before handing dispositions to the rabbit-feedback-resolver skill. - Rate-limit degradation: Treats CodeRabbit quota limits as a waiver for future passes only, requiring every already-delivered thread to be settled before recording the gate as skipped. - Use Case: After pushing fixes to a PR, run the waiter in the background, triage the new threads it surfaces, dispatch the resolver with per-thread dispositions, and loop until the check passes with zero unresolved threads. ## Quick Start Wait for the CodeRabbit review on pull request 42, triage its findings against my Scope Brief, and resolve every thread until the check settles clean.

Frequently Asked Questions about coderabbit-review

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

FAQPage Schema
How do I wait for a CodeRabbit review to finish on a pull request?▼

Run the bundled wait-for-coderabbit-review.sh script in the background with the PR number, redirecting output to a log file. It polls the CodeRabbit check and ends with a STATUS line such as TERMINAL_PASS or PENDING that you branch on.

How do I resolve CodeRabbit review comments on a GitHub PR?▼

Fetch the review threads with a paginated gh api graphql call, triage each thread as blocking, immaterial, or deferred against your Scope Brief, then dispatch the rabbit-feedback-resolver skill with those per-thread dispositions so it replies and resolves each one.

What happens when CodeRabbit is rate-limited during a review?▼

Rate limiting waives only the review passes that never ran. You must still fix every blocking finding already delivered and settle every posted thread, then record the gate as skipped (rate-limited) and continue without retrying or waiting.

Why does the CodeRabbit waiter report NOT_CONFIGURED?▼

NOT_CONFIGURED means no CodeRabbit check appeared on the PR after a grace period, so the GitHub App is not installed for that repository. This is terminal and expected for most repos; report it once and proceed without retrying.

Can I use gh pr view reviews to check CodeRabbit status?▼

No. The skill forbids raw gh api reviews or gh pr view --json reviews for merge decisions because they do not reflect the check state and unresolved threads accurately. Use the bundled wait script, which reads the check and counts unresolved threads with fail-closed semantics.