Agent skill · marketing growth · jeremylongshore
coderabbit-enterprise-rbac
Design and audit roles, seats, API access, and administrative separation for an enterprise organization. Use when this operator task needs a current, evidence-backed CodeRabbit workflow. Trigger with "audit CodeRabbit RBAC".
Why this skill is useful
Provides specific configuration patterns and management strategies for CodeRabbit enterprise access control that the AI wouldn't reliably generate on its own.
What it needs
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 Enterprise RBAC Overview Use CodeRabbit native administrative roles instead of inferring all access from the Git provider. Map developer seats and administrative authority separately. 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 Built-in roles are Admin, Member, and Billing Admin. CodeRabbit roles are independent of Git roles after initial assignment. Billing Admin does not consume a seat and cannot edit role matrices. Enterprise custom roles expose granular permissions. 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. Inventory users, provider roles, CodeRabbit roles, seats, keys, and repo access. 2. Map job functions to least privilege across settings, billing, reports, API, and logs. 3. Find toxic combinations, stale admins, unused seats, and unmanaged keys. 4. Draft changes with partial-success handling, rollback, and recertification. 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-enterprise-rbac