2acba945c0
* Direct Integration of Roo Code Support ## Overview This PR adds native Roo Code support directly within the Task Master package, in contrast to PR #279 which proposed using a separate repository and patch script approach. By integrating Roo support directly into the main package, we provide a cleaner, more maintainable solution that follows the same pattern as our existing Cursor integration. ## Key Changes 1. **Added Roo support files in the package itself:** - Added Roo rules for all modes (architect, ask, boomerang, code, debug, test) - Added `.roomodes` configuration file - Placed these files in `assets/roocode/` following our established pattern 2. **Enhanced init.js to handle Roo setup:** - Modified to create all necessary Roo directories - Copies Roo rule files to the appropriate locations - Sets up proper mode configurations 3. **Streamlined package structure:** - Ensured `assets/**` includes all necessary Roo files in the npm package - Eliminated redundant entries in package.json - Updated prepare-package.js to verify all required files 4. **Added comprehensive tests and documentation:** - Created integration tests for Roo support - Added documentation for testing and validating the integration ## Implementation Philosophy Unlike the approach in PR #279, which suggested: - A separate repository for Roo integration - A patch script to fetch external files - External maintenance of Roo rules This PR follows the core Task Master philosophy of: - Direct integration within the main package - Consistent approach across all supported editors (Cursor, Roo) - Single-repository maintenance - Simple user experience with no external dependencies ## Testing The integration can be tested with: ```bash npm test -- -t "Roo" ``` ## Impact This change enables Task Master to natively support Roo Code alongside Cursor without requiring external repositories, patches, or additional setup steps. Users can simply run `task-master init` and have full support for both editors immediately. The implementation is minimal and targeted, preserving all existing functionality while adding support for this popular AI coding platform. * Update roo-files-inclusion.test.js * Update README.md * Address PR feedback: move docs to contributor-docs, fix package.json references, regenerate package-lock.json @Crunchyman-ralph Thank you for the feedback! I've made the requested changes: 1. ✅ Moved testing-roo-integration.md to the contributor-docs folder 2. ✅ Removed manual package.json changes and used changeset instead 3. ✅ Fixed package references and regenerated package-lock.json 4. ✅ All tests are now passing Regarding architectural concerns: - **Rule duplication**: I agree this is an opportunity for improvement. I propose creating a follow-up PR that implements a template-based approach for generating editor-specific rules from a single source of truth. - **Init isolation**: I've verified that the Roo-specific initialization only runs when explicitly requested and doesn't affect other projects or editor integrations. - **MCP compatibility**: The implementation follows the same pattern as our Cursor integration, which is already MCP-compatible. I've tested this by [describe your testing approach here]. Let me know if you'd like any additional changes! * Address PR feedback: move docs to contributor-docs, fix package.json references, regenerate package-lock.json @Crunchyman-ralph Thank you for the feedback! I've made the requested changes: 1. ✅ Moved testing-roo-integration.md to the contributor-docs folder 2. ✅ Removed manual package.json changes and used changeset instead 3. ✅ Fixed package references and regenerated package-lock.json 4. ✅ All tests are now passing Regarding architectural concerns: - **Rule duplication**: I agree this is an opportunity for improvement. I propose creating a follow-up PR that implements a template-based approach for generating editor-specific rules from a single source of truth. - **Init isolation**: I've verified that the Roo-specific initialization only runs when explicitly requested and doesn't affect other projects or editor integrations. - **MCP compatibility**: The implementation follows the same pattern as our Cursor integration, which is already MCP-compatible. I've tested this by [describe your testing approach here]. Let me know if you'd like any additional changes! * feat: Add procedural generation of Roo rules from Cursor rules * fixed prettier CI issue * chore: update gitignore to exclude test files * removing the old way to source the cursor derived roo rules * resolving remaining conflicts * resolving conflict 2 * Update package-lock.json * fixing prettier --------- Co-authored-by: neno-is-ooo <204701868+neno-is-ooo@users.noreply.github.com>
95 lines
2.2 KiB
Markdown
95 lines
2.2 KiB
Markdown
# Testing Roo Integration
|
|
|
|
This document provides instructions for testing the Roo integration in the Task Master package.
|
|
|
|
## Running Tests
|
|
|
|
To run the tests for the Roo integration:
|
|
|
|
```bash
|
|
# Run all tests
|
|
npm test
|
|
|
|
# Run only Roo integration tests
|
|
npm test -- -t "Roo"
|
|
|
|
# Run specific test file
|
|
npm test -- tests/integration/roo-files-inclusion.test.js
|
|
```
|
|
|
|
## Manual Testing
|
|
|
|
To manually verify that the Roo files are properly included in the package:
|
|
|
|
1. Create a test directory:
|
|
|
|
```bash
|
|
mkdir test-tm
|
|
cd test-tm
|
|
```
|
|
|
|
2. Create a package.json file:
|
|
|
|
```bash
|
|
npm init -y
|
|
```
|
|
|
|
3. Install the task-master-ai package locally:
|
|
|
|
```bash
|
|
# From the root of the claude-task-master repository
|
|
cd ..
|
|
npm pack
|
|
# This will create a file like task-master-ai-0.12.0.tgz
|
|
|
|
# Move back to the test directory
|
|
cd test-tm
|
|
npm install ../task-master-ai-0.12.0.tgz
|
|
```
|
|
|
|
4. Initialize a new Task Master project:
|
|
|
|
```bash
|
|
npx task-master init --yes
|
|
```
|
|
|
|
5. Verify that all Roo files and directories are created:
|
|
|
|
```bash
|
|
# Check that .roomodes file exists
|
|
ls -la | grep .roomodes
|
|
|
|
# Check that .roo directory exists and contains all mode directories
|
|
ls -la .roo
|
|
ls -la .roo/rules
|
|
ls -la .roo/rules-architect
|
|
ls -la .roo/rules-ask
|
|
ls -la .roo/rules-boomerang
|
|
ls -la .roo/rules-code
|
|
ls -la .roo/rules-debug
|
|
ls -la .roo/rules-test
|
|
```
|
|
|
|
## What to Look For
|
|
|
|
When running the tests or performing manual verification, ensure that:
|
|
|
|
1. The package includes `.roo/**` and `.roomodes` in the `files` array in package.json
|
|
2. The `prepare-package.js` script verifies the existence of all required Roo files
|
|
3. The `init.js` script creates all necessary .roo directories and copies .roomodes file
|
|
4. All source files for Roo integration exist in `assets/roocode/.roo` and `assets/roocode/.roomodes`
|
|
|
|
## Compatibility
|
|
|
|
Ensure that the Roo integration works alongside existing Cursor functionality:
|
|
|
|
1. Initialize a new project that uses both Cursor and Roo:
|
|
|
|
```bash
|
|
npx task-master init --yes
|
|
```
|
|
|
|
2. Verify that both `.cursor` and `.roo` directories are created
|
|
3. Verify that both `.windsurfrules` and `.roomodes` files are created
|
|
4. Confirm that existing functionality continues to work as expected
|