Agent skill · software engineering · jeremylongshore
coderabbit-multi-env-setup
Design behavior for default, development, release, and hotfix targets using supported auto-review controls. Use when this operator task needs a current, evidence-backed CodeRabbit workflow. Trigger with "configure CodeRabbit by branch".
Why this skill is useful
Adds specific configuration patterns for CodeRabbit 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 Branch and Environment Policy Overview Model environments as policy inputs, not separate deployments. Feature-branch YAML supplies config; auto-review controls target eligibility. 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 Repository YAML is read from the feature branch. The default target is always included when auto-review is enabled. basebranches adds target branches with regex patterns. Central, repo, organization, and global authorities have precedence. 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 branch patterns, risk, merge rules, and config authorities. 2. Define targets, drafts, labels, ignored authors, and path guidance. 3. Validate regexes and resolved feature-branch config on synthetic PRs. 4. Promote only after default, release, exclusion, and rollback cases pass. 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-multi-env-setup--a6c049