Agent skill · software engineering · jeremylongshore
coderabbit-migration-deep-dive
Migrate from another review process through measured coexistence, control mapping, and reversible cohorts. Use when this operator task needs a current, evidence-backed CodeRabbit workflow. Trigger with "migrate to CodeRabbit".
Why this skill is useful
Provides specific migration scripts and configuration mappings for transitioning to CodeRabbit from various code review tools that the AI wouldn't reliably generate on its own.
What it needs
Requires gh 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 Adoption Migration Overview Preserve every existing control until its replacement is proven. Translate outcomes and ownership instead of assuming one-to-one fields. 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 CodeRabbit spans PR, CLI or IDE, tools, knowledge, and optional actions. Configuration can be centralized and inherited. Plan and provider support differ. Existing human, CI, security, and compliance controls remain authoritative. 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 current tools, rules, checks, data controls, costs, metrics, and owners. 2. Map each control to supported capability, retained control, or gap. 3. Run coexistence in a representative pilot. 4. Approve cohorts only when coverage and rollback evidence 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. Approval Boundaries Require security, repository, and business owners before replacing a required control. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/coderabbit-migration-deep-dive--cbc2d6