Agent skill · software engineering · jeremylongshore
coderabbit-core-workflow-a
Run the primary CodeRabbit review loop from eligibility through finding disposition and verification. Use when this operator task needs a current, evidence-backed CodeRabbit workflow. Trigger with "run a CodeRabbit PR review".
Why this skill is useful
Adds a complete executable workflow configuration for automated PR reviews that includes specific review instructions and settings not found in public documentation.
What it needs
Requires coderabbit 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 Pull Request Review Overview Operate one evidence-backed review cycle. Separate walkthroughs, inline findings, incremental review, full review, CI, and human merge ownership. 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 Eligible pull requests are reviewed automatically unless configuration excludes them. The walkthrough is separate from inline findings. Incremental and full reviews are distinct commands. CodeRabbit supplements rather than replaces required CI and human judgment. 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. Verify installation, eligibility, feature-branch config, and independent CI. 2. Group walkthrough and inline findings by severity, file, and evidence. 3. Resolve valid findings in bounded commits and explain declined findings. 4. Request the appropriate documented review and confirm closure before handoff. 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-core-workflow-a