Index of every page on this site: llms.txt
All skills
coderabbitai avatar

/coderabbit-config

@d8e182b official
by CodeRabbitcoderabbitai/skills222 stars
25
Run it yourself

Create, update, or validate CodeRabbit repository configuration through the official CLI. Use for .coderabbit.yaml or .coderabbit.yml setup, review-style changes, path guidance, and configuration validation requests.

Use this Skill: https://skilld.dev/gh/coderabbitai/skills/coderabbit-config

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈59 tokens for metadata: the name and description. ≈1.4k when used: this file.

Description uses 2.9% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈236 characters, or 2.9%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

CodeRabbit Configuration

Requires config protocol v2, a Git working tree, and network access to the current configuration schema.

Keep configuration generation, schema validation, previews, and repository writes in the CLI. Do not edit repository YAML yourself, copy a schema, or implement a fallback editor. Configuration is local; it does not need CodeRabbit login or start a review.

Find the CLI and requested repository

Use the intended Git working tree for every invocation. Select the installed workflow before looking for a standalone CLI:

  • Packages without a managed runtime use the standalone CLI discovery below. A remote MCP connection does not provide a managed local runtime.
  • For another installed package that explicitly declares a managed runtime, use its verified launcher and preparation instructions.
  • For standalone installs, resolve an official installed coderabbit to a quoted canonical absolute path, checking PATH and the documented installer location ~/.local/bin/coderabbit on macOS/Linux. Reject repository-local executables, aliases, and unknown wrappers. If the installation source is uncertain, ask the user to identify their installation. A source checkout's cli.json alone does not select a managed runtime.

The <cli> examples below mean that verified executable, not a literal command.

Check <cli> --version, <cli> config --help, and support for the needed subcommands. CLI 0.9.3 supports this workflow. Missing commands or an unsupported protocol require an upgrade. For a standalone CLI, follow the official installation instructions for its actual installation method (for example, brew upgrade coderabbit for Homebrew). For a managed runtime, update the plugin to a version with a compatible pinned CLI and follow its preparation instructions; never run <cli> update on the managed launcher. Do not install or upgrade without authorization. Preserve permission and network errors as such; they do not prove an upgrade is needed. After any upgrade, repeat trusted executable discovery and verification, then recheck version and command support. Do not reuse the old canonical path: an upgrade can replace a versioned installation directory or managed launcher.

Validate only

Run <cli> config validate --agent for the repository configuration, or <cli> config validate <file> --agent for the user's explicitly selected YAML file. Require exit zero and ok: true; report the CLI's validation diagnostics otherwise. Do not generate or apply changes for a validation-only request.

Create or change review style

  1. Run <cli> config --agent. Require exit zero, ok: true, protocolVersion: 2, operation: inspect, and writable: true. Preserve the returned repository root, target, and baseHash (none for a new file). Respect authority warnings, including TypeScript, remote configuration, symlinks, and multiple YAML files; do not delete or bypass them.
  2. Run <cli> config --agent --generate. For a requested style, add --profile chill (Balanced), --profile quiet (Focused), --profile assertive (Thorough), or --profile default (remove the local style override). Without a profile, the CLI generates its baseline for a new file and preserves an existing file. Do not infer a style change from a general request to check configuration.
  3. Require a successful protocol-v2 operation: generate response with the inspected target and base hash. Copy its exact after string into a temporary proposal file outside the repository; do not rewrite or extend that YAML.
  4. Preview with <cli> config apply <proposal> --agent --dry-run --base <baseHash>. Require exit zero and a successful protocol-v2 operation: apply result. If unchanged, re-inspect the same base hash and report that no save is needed. Otherwise show the returned before/after diff and obtain approval for it.
  5. Save the same proposal with <cli> config apply <proposal> --agent --yes --base <baseHash>. Require a successful protocol-v2 result with applied: true. Re-inspect and verify the target and saved hash against the approved proposedHash, then report the local change. Remove your temporary proposal; preserve any CLI-reported recovery file.

On changed input, inspect and preview again instead of bypassing the base hash. On schema, validation, permission, or network errors, report the diagnostic and stop without an alternate writer. An interrupted save has an unknown outcome: inspect the file before retrying or reporting success.

Guided path settings

For path-guidance requests, run <cli> config --detailed in an interactive terminal to enter the manual review-style and path-guidance flow directly. For general interactive setup, use <cli> config or <cli> config --generate. Relay the CLI's actual prompts and preview, using settled user preferences and asking for missing choices. Confirm the displayed changes only after approval. If the host cannot interact with a terminal, give the user the exact command to run in the selected repository and resume after they finish. Do not simulate the wizard with piped answers. For settings the installed CLI cannot edit, explain the capability gap instead of inventing flags or editing YAML yourself.

After a successful save, validate and inspect the resulting configuration. Saving locally does not activate settings on hosted PR reviews. Commit, push, dashboard changes, and running a review require their own user-requested scope.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2d3 checks · Risk SAFE
  • Gen Agent Trust Hub2d

    The skill facilitates repository configuration management using the official CodeRabbit CLI. It includes several security-positive instructions, such as verifying the CLI binary path, rejecting untrusted wrappers, and requiring user approval for all changes.

  • Socket2d

    No alerts

  • Snyk2d

    Risk: LOW · No issues

Signed by skilld at d8e182b. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 2 days ago.

Activeupdated 3 days ago
metadata
{
  "version": "0.1.0"
}

README badge

README badge for coderabbitai/skills/coderabbit-config