Add a CLI-backed CodeRabbit config skill

[nehal-a2z]

Problem

Users should be able to ask their coding agent to create, update, or validate CodeRabbit repository configuration without each agent reimplementing the YAML schema, defaults, prompts, or file mutation behavior.

Proposal

Add a portable config skill that is a thin routing layer over the official CodeRabbit CLI:

• Create or update: coderabbit config (or explicit coderabbit config --generate)
• Validate: coderabbit config --validate [file]
• Let the CLI own prompts, precedence warnings, schema checks, previews, confirmations, and writes.
• Do not add YAML editing, schema copies, or a fallback implementation to the skill.

Acceptance criteria

• The skill activates for configuration create, update, and validation requests, including $config or /config where supported.
• Missing CLI support produces an upgrade instruction rather than an agent-side fallback.
• Public documentation and supported distribution manifests describe the new skill.
• The skill is not published before the required CLI commands are available in an official release.

[coderabbitai]

🔗 Related PRs

#23 - fix(skills): align review guidance with CLI 0.7 [open]
#25 - fix(code-review): respect agent execution contexts [open]
#26 - chore: add repository CodeRabbit policy [merged]
#33 - fix(code-review): harden host auth boundary [open]
#34 - refactor: autofix skill (tools: edited autofix + devclarityai/devclarity-marketplace:skill-improver) [open]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!