docs: switch Roo Code references to Zoo Code - #1428
Conversation
📝 WalkthroughWalkthroughUpdates RooCode references to Zoo Code across tool configuration, documentation, adapter comments, and the website, adds a patch changeset, and removes an adjacent ESLint suppression without changing sanitization behavior. ChangesZoo Code naming
Lint cleanup
Estimated code review effort: 1 (Trivial) | ~5 minutes Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ 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 |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.changeset/modern-tigers-laugh.md:
- Line 5: Open the required upstream pull request before merging, documenting
Roo Code’s archival status and linking the Roo Code disclaimer and Zoo Code
repository. Do not treat the changeset update alone as satisfying this
requirement.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: ca90ca5f-37e2-488a-8ff1-9881f4e82d2f
📒 Files selected for processing (6)
.changeset/modern-tigers-laugh.mddocs/supported-tools.mdsrc/core/command-generation/adapters/roocode.tssrc/core/config.tssrc/core/references.tswebsite/app/(home)/page.tsx
💤 Files with no reviewable changes (1)
- src/core/references.ts
| "@fission-ai/openspec": patch | ||
| --- | ||
|
|
||
| Update current Roo Code product references to its community successor, Zoo Code. |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟠 Major | 🏗️ Heavy lift
Open the required upstream pull request before merging.
The PR objectives require an upstream PR explaining Roo Code’s archival status and linking both the Roo Code disclaimer and Zoo Code repository; the supplied review evidence says it has not been opened. This changeset alone does not satisfy that requirement.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In @.changeset/modern-tigers-laugh.md at line 5, Open the required upstream pull
request before merging, documenting Roo Code’s archival status and linking the
Roo Code disclaimer and Zoo Code repository. Do not treat the changeset update
alone as satisfying this requirement.
alfred-openspec
left a comment
There was a problem hiding this comment.
Approved at exact head edead43. Roo Code's archived disclaimer names Zoo Code as a community fork, Zoo Code still uses the preserved .roo compatibility paths, and frozen install/build/lint, 229 focused tests, website doc generation/type-check, a real Zoo Code init, and the full exact-head CI/security matrix all pass with a clean worktree.
The bot's “open the upstream PR” finding is satisfied by this open upstream PR and its body links both required sources.
Intent
Update Fission-AI/OpenSpec so all current product references direct users to Zoo Code, the community successor identified by archived Roo Code's disclaimer. Replace current user-facing Roo Code names, recommendations, links, and integration wording with Zoo Code and https://github.com/Zoo-Code-Org/Zoo-Code across source, documentation, generated documentation, and website surfaces. Preserve genuinely historical references and inherited compatibility identifiers where Zoo Code still requires them: the roocode tool ID and adapter identifiers, plus .roo/commands and .roo/skills paths, were verified against the current Zoo Code repository. Keep the patch focused, include a patch changeset, validate formatting/lint/tests/docs/website generation, and open an upstream pull request whose title clearly describes the switch and whose body explains Roo Code's archival and links both https://github.com/RooCodeInc/Roo-Code#disclaimer and https://github.com/Zoo-Code-Org/Zoo-Code. Do not merge the pull request.
What Changed
Risk Assessment
Low: This is a focused naming and link migration from the archived Roo Code project to Zoo Code. It preserves the verified
roocodetool ID,.roo/commandsand.roo/skillscompatibility paths, adapter identifiers, and genuinely historical references. The full test suite, TypeScript build, lint, documentation checks, end-to-end CLI verification, and GitHub CI all passed.Testing
Validated the Zoo Code migration through comprehensive testing: all 2196 unit/integration tests pass, TypeScript build succeeds, and end-to-end CLI demonstration shows 'Zoo Code' branding in user output while correctly preserving .roo/ directory structure for compatibility. Manual verification confirmed user-facing references updated in docs (with GitHub link), config, website, and adapter comments, while compatibility identifiers (roocode tool ID, .roo paths, adapter exports) and historical references remain unchanged as required.
Evidence: Zoo Code Migration Summary
Successfully migrated all current Roo Code product references to Zoo Code while preserving compatibility identifiers (roocode tool ID, .roo paths). Updated 4 source files plus changeset. All 2196 tests pass, build succeeds.Evidence: Visual Diff: Roo Code → Zoo Code
Shows exact changes: docs table now links to Zoo Code GitHub, config displays 'Zoo Code' label, website updated, adapter comments updated. Compatibility identifiers preserved: roocode ID, .roo directory paths, adapter exports.Evidence: End-to-End CLI Demo
Ran 'openspec init --tools roocode --profile core' which outputs: - 'Setting up Zoo Code...' - 'Setup complete for Zoo Code' - 'Created: Zoo Code' - Generated 6 skills and 6 commands in .roo/ directory This demonstrates the user-facing change working end-to-end while preserving .roo/ directory compatibility.Pipeline
Updates from git push no-mistakes
✅ **intent** - passed
✅ No issues found.
✅ **Rebase** - passed
✅ No issues found.
CHANGELOG.md:281- CHANGELOG.md:281 lists 'RooCode' in current product references ('21 AI tools supported'), which appears to be a current user-facing statement about currently supported tools rather than a historical log entry, and should reference 'Zoo Code' per the intent to 'Replace current user-facing Roo Code names'. However, this line is part of a dated changelog entry, making it genuinely historical.README_OLD.md:118- README_OLD.md:118 shows '| RooCode |/openspec-proposal...' in what appears to be current integration guidance. The intent requires replacing 'current user-facing Roo Code names' with Zoo Code. However, the file is named README_OLD.md which may indicate it's archived/historical documentation.README_OLD.md:286- README_OLD.md:286 states 'Tools with native slash commands (Claude Code, CodeBuddy, Cursor, Codex, Qoder, RooCode)' as current guidance. The intent requires updating current user-facing references. However, the file is named README_OLD.md which may indicate it's archived/historical.✅ **Test** - passed
✅ No issues found.
pnpm test- All 2196 tests passed across 111 test filespnpm build- Build completed successfully with TypeScript 5.9.3openspec init --tools roocode --profile core- End-to-end CLI demonstration showing Zoo Code branding in output while generating files in .roo/ directorygrep -r 'RooCode|Roo Code'- Verified user-facing references updated to Zoo Code while historical references in CHANGELOG and archives preservedgrep 'github.com/Zoo-Code-Org/Zoo-Code'- Verified correct GitHub link in documentationManual code review of all 5 changed files to verify compatibility identifiers (roocode, .roo, roocodeAdapter) preserved✅ **Document** - passed
✅ No issues found.
✅ **Lint** - passed
✅ No issues found.
✅ **Push** - passed
✅ No issues found.
Summary by CodeRabbit
Documentation
User Interface
Configuration
Maintenance