Agent skill · software engineering · jeremylongshore
coderabbit-rate-limits
Analyze PR, IDE, and CLI limits using the current per-developer hourly contract and usage evidence. Use when this operator task needs a current, evidence-backed CodeRabbit workflow. Trigger with "check CodeRabbit rate limits".
Why this skill is useful
Adds executable scripts for handling GitHub API rate limits and CodeRabbit command limits that aren't in public docs.
What it needs
Requires gh installed locally. Requires github account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
CodeRabbit Review Rate Limits Overview Use current dashboard and responses instead of stale concurrency tables. Separate CodeRabbit allowances, file limits, credits, and provider API limits. Prerequisites Identify the CodeRabbit organization, Git provider, repository, plan, and accountable owner. Read references/official-docs.md and re-check any time-sensitive contract before execution. Use synthetic or read-only evidence until the approval boundary is satisfied. Preserve the repository's independent CI, security, and human-review requirements. Current Contract The current plan table defines reviews per developer per hour and files per review. Allowances refill under the documented model. @coderabbitai rate limit reports PR quota without a review. The usage-based add-on can continue eligible reviews with credits. Authentication Treat Git-provider sessions, CodeRabbit web sessions, CLI credentials, and CodeRabbit API keys as separate credentials. Use only an already-approved session or secret-manager reference, never print a secret, and do not place credentials in .coderabbit.yaml, source files, logs, or deliverables. Instructions 1. Capture user, org, plan, surface, time, response, Review Log, files, and allowance. 2. Classify allowance, file limit, credit state, provider limit, or service failure. 3. Reduce avoidable events or present a dated capacity decision. 4. Retry only after documented refill or approved change. Tool Discipline Use Glob to locate candidate configuration and evidence files without widening scope. Use Grep to find relevant fields, commands, identifiers, and stale claims. Use Read to inspect the smallest required files and authoritative evidence. Use Write only for a new approved local draft or evidence artifact. Use Edit only for a bounded approved change whose rollback is known. Do not use these file tools as a substitute for authenticated CodeRabbit or provider operations. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/coderabbit-rate-limits