## 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.