Agent skill · software engineering · jeremylongshore
coderabbit-local-dev-loop
Operate CLI reviews inside an agentic coding loop with bounded diffs, current authentication, and fix verification. Use when this operator task needs a current, evidence-backed CodeRabbit workflow. Trigger with "review local changes with CodeRabbit".
Why this skill is useful
Adds specific CLI commands and configuration patterns for integrating CodeRabbit into local development workflows that the AI wouldn't reliably generate on its own.
What it needs
Requires coderabbit installed locally. Requires coderabbit account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
CodeRabbit Local Review Loop Overview Use the native CLI before push and feed findings back into coding. Keep auth, scope, and spend visible. 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 CLI reviews local changes before commit. coderabbit review --plain is the agent-friendly command. Interactive and Agentic-key login are distinct. CLI allowances and billing follow current plan contracts. 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. Confirm repo state, diff scope, auth mode, allowance, and excluded files. 2. Run a bounded plain review and capture findings without secrets. 3. Classify findings, fix approved items, and rerun changed scope. 4. Stop on repeats, scope expansion, auth errors, or usage limits. 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. Approval Boundaries Require approval before credits, headless keys, wider review scope, or pushing. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/coderabbit-local-dev-loop--94329d