coderabbit-rate-limit-retry

Detects CodeRabbit rate-limit comments on GitHub PRs and retries the review after the cooldown.

1|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/CoderCoco-Studios/Hyveon --skill coderabbit-rate-limit-retry-codercoco-studios
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coderabbit-rate-limit-retry
Source: https://github.com/CoderCoco-Studios/Hyveon/tree/main/.claude/skills/coderabbit-rate-limit-retry
Command: npx skills add https://github.com/CoderCoco-Studios/Hyveon --skill coderabbit-rate-limit-retry-codercoco-studios

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? CodeRabbit sometimes replies to a pull request with a "Review limit reached" comment instead of an actual review, leaving the PR stuck. This Skill reads that comment, computes the real remaining cooldown from the comment's timestamp, waits it out, and re-triggers the review with @coderabbitai review. ## Core Features & Use Cases - Accurate cooldown calculation: Parses the comment's createdAt timestamp and stated cooldown (minutes or hours) to compute the true remaining wait, plus a safety buffer. - Non-blocking waits: Runs short waits as backgrounded shell commands and defers long waits to scheduling, so the conversation is never stuck idle. - Bounded retries: Caps re-trigger attempts at 3 per invocation and re-reads each new rate-limit comment fresh, avoiding infinite retry loops. - Use Case: A PR shows CodeRabbit's "Review limit reached" comment posted 8 minutes ago with a 15-minute cooldown. The Skill computes ~7 minutes remaining, sleeps in the background, then posts @coderabbitai review to unblock the review. ## Quick Start Check PR #42 for a CodeRabbit rate-limit comment and retry the review once the cooldown has elapsed.

Frequently Asked Questions about coderabbit-rate-limit-retry

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

FAQPage Schema
How do I retry a CodeRabbit review after a rate limit?

Find the bot's "Review limit reached" comment on the PR, compute the remaining cooldown from its creation timestamp, wait that duration plus a small buffer, then post `@coderabbitai review` as a PR comment to re-trigger the review.

How is the CodeRabbit cooldown wait time calculated?

The cooldown is measured from when CodeRabbit posted the comment, not when you read it. Add the stated minutes or hours to the comment's createdAt timestamp, subtract the current time, and add a 30-60 second safety buffer.

Can I trigger a CodeRabbit review without a rate-limit comment?

You should not. Posting `@coderabbitai review` speculatively wastes a review on paid plans or does nothing on unpaid ones. Always confirm an active rate-limit comment exists before re-triggering.

What happens if CodeRabbit rate limits the retry again?

The Skill re-reads the new rate-limit comment and repeats the wait-and-retry flow, but caps total attempts at 3 per invocation. After the cap, it reports the latest available-at time and stops instead of spawning more background retries.

Does the retry block the conversation while waiting?

No. Short waits run as a backgrounded `sleep && gh pr comment` command so work continues, and long waits are deferred by telling the user the available-at time or using a scheduling skill instead of holding an open sleep.