feat: add Roo Code IDE support - #49
Conversation
Closes #32 Add support for the Roo Code VS Code extension (rooveterinaryinc.roo-cline). Instructions are installed to .roo/rules/*.md with recursive directory reading. Roo Code supports MCP servers (.roo/mcp.json), slash commands (.roo/commands/), mode-specific rules, and both global and project scope. - New RooTool class with global and project-level instruction support - Cross-platform detection (macOS, Linux, Windows) - IDE capability registry entry (instructions, MCP, commands, resources) - Component detector recognizes .roo/rules/ directories - Full test coverage for Roo Code tool integration - Updated documentation and version bump to 0.5.3
📊 Code Quality ReportLinting Issues |
Coverage report
Click to see where and how coverage changed
This report was generated by python-coverage-comment-action |
||||||||||||||||||||||||||||||||||||||||||||||||||||||
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #49 +/- ##
==========================================
+ Coverage 75.18% 75.30% +0.11%
==========================================
Files 67 68 +1
Lines 7106 7150 +44
==========================================
+ Hits 5343 5384 +41
- Misses 1763 1766 +3 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: fc5ff9931f
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| "MCP configured globally via cline_mcp_settings.json, no project-level MCP support." | ||
| ), | ||
| ), | ||
| AIToolType.ROO: IDECapability( |
There was a problem hiding this comment.
Registering AIToolType.ROO in the capability registry makes Roo look fully supported for package installation, but install_package() always calls get_translator(target_ide) and aiconfigkit/ai_tools/translator.py#get_translator has no Roo entry, so --ide roo now fails with ValueError before any components are installed. This is a hard failure for the new Roo package flow and should be fixed by adding a Roo translator (or gating Roo out of this path until one exists).
Useful? React with 👍 / 👎.
| ".windsurf/rules": "windsurf", | ||
| ".kiro/steering": "kiro", | ||
| ".clinerules": "cline", | ||
| ".roo/rules": "roo", |
There was a problem hiding this comment.
Adding .roo/rules here routes Roo instructions through _detect_instructions(), but that function only uses recursive traversal for Copilot and otherwise calls iterdir(), so nested Roo rule files are silently skipped. Roo rules are documented in this change as recursive, so package creation from projects using subdirectories under .roo/rules/ will miss instructions.
Useful? React with 👍 / 👎.
1 participant
Summary
rooveterinaryinc.roo-cline).roo/rules/*.mdwith recursive reading.roo/mcp.json), slash commands (.roo/commands/), and both global/project scope.roo/rules/directoriesCloses #32
Test plan