Agent skill · software engineering · jeremylongshore
coderabbit-install-auth
Analyze and implement platform installation plus interactive or headless CLI authentication with least privilege. Use when this operator task needs a current, evidence-backed CodeRabbit workflow. Trigger with "install CodeRabbit".
Why this skill is useful
Adds specific installation scripts and configuration patterns for integrating CodeRabbit with GitHub and GitLab that the AI wouldn't reliably generate on its own.
What it needs
Requires curl, gh installed locally. Requires github, gitlab account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
CodeRabbit Installation and Authentication Overview Route setup through the provider-specific flow and separate web-app installation from CLI auth. Never solicit or print credentials. 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 GitHub, GitLab, Azure DevOps, and Bitbucket use different authorization contracts. Organization access may require admin approval and explicit repo scope. Interactive and headless Agentic-key CLI auth are separate. Headless keys belong in a secret store, not repository config. 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. Identify provider, hosting, owner, repositories, data class, plan, and surface. 2. Review permissions and choose the smallest installation scope. 3. Complete user-driven authorization or approved secret-store headless auth. 4. Verify one bounded review and record permissions and rotation owner. 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-install-auth