Agent skill · software engineering · jeremylongshore
coderabbit-upgrade-migration
Analyze and upgrade configuration, plan-enabled features, tools, or platform integration through schema validation and reversible rollout. Use when this operator task needs a current, evidence-backed CodeRabbit workflow. Trigger with "upgrade CodeRabbit configuration".
Why this skill is useful
Provides specific YAML configuration patterns and migration steps for CodeRabbit 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 Configuration Upgrade Overview Treat managed-SaaS upgrades as configuration and entitlement changes, not SDK versions. Revalidate docs because contracts evolve. 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 current schema URL is https://coderabbit.ai/integrations/schema.v2.json. The configuration reference is generated from that schema. The YAML validator checks proposed configuration. Plan, provider, early-access, and self-hosted changes are separate. 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. Capture resolved config, schema validity, plan, provider, features, metrics, and rollback. 2. Identify added, removed, renamed, defaulted, or gated behavior. 3. Apply the smallest feature-branch change and test eligible and excluded cases. 4. Canary, compare evidence, then promote or revert. 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-upgrade-migration--452cc7