feat: add Mistral Vibe as a supported tool#1114
Conversation
Vibe uses the SKILL.md standard natively. Skills install to ~/.vibe/skills/ (global) or .vibe/skills/ (project-local via skill_paths config). No command adapter exists — skill-based invocations only. Adds the `vibe` tool ID to AI_TOOLS in config.ts and the corresponding row in docs/supported-tools.md with a footnote explaining the skill_paths setup step. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThis PR registers Vibe (Mistral) as an available AI tool by adding a configuration entry and updating documentation. The configuration defines the tool's identifier and skills directory, while the docs describe tool availability and explain Vibe's global skills loading behavior with project-local override options. ChangesVibe Tool Registration
Estimated code review effort🎯 2 (Simple) | ⏱️ ~5 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
AI_TOOLSarray insrc/core/config.tswithskillsDir: '.vibe'docs/supported-tools.mdvibeto the--toolsID list~/.vibe/skills/by default, and project-local.vibe/skills/requires adding the path toskill_pathsin~/.vibe/config.tomlNotes
Vibe uses the SKILL.md standard natively (same frontmatter format). Skills are invoked as
/skill-namecommands. No command adapter exists — commands are "Not generated", consistent with Trae and ForgeCode.This was surfaced while adding nanopm as a community schema (PR #1109) — nanopm now ships Vibe-translated skills and installs to
~/.vibe/skills/automatically. Vibe being absent from this list was the gap.Test plan
openspec init --tools vibeinstalls skills to.vibe/skills/openspec-*/SKILL.mdopenspec init --tools allincludes Vibevibeappears in--helptool ID list🤖 Generated with Claude Code
Summary by CodeRabbit
New Features
Documentation