ros/claude-task-master
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

update "brand rules" to "rules"

Browse Source
This commit is contained in:
Joe Danziger
2025-05-22 14:26:08 -04:00
parent 0c64e9a739
commit c5c46e0cf8
9 changed files with 54 additions and 115 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
.changeset/lemon-deer-hide.md
View File

@@ -2,14 +2,14 @@
'task-master-ai': patch
---
Added flexible brand rules management:
Added flexible rules management:
- New `init` flag: You can now specify which brands to include rules for at project initialization using `--rules <brands>` or `-r <brands>` (e.g., `task-master init -r cursor,roo`). Only the selected brands' rules and configuration are included.
- New commands: `task-master rules add <brands>` and `task-master rules remove <brands>` let you add or remove brand-specific rules and MCP config after initialization, supporting multiple brands at once.
- New command: `task-master rules setup` launches an interactive prompt to select which brand rules to apply to your project. This does **not** re-initialize your project or affect shell aliases; it only manages rules. The list of brands is always up-to-date with available profiles, so you never have to update the CLI when adding a new brand.
- The interactive rules setup flow is also used during `init` if you don't specify brands with `--rules`.
- New `init` flag: You can now specify which rules to include at project initialization using `--rules <rules>` or `-r <rules>` (e.g., `task-master init -r cursor,roo`). Only the selected rules and configuration are included.
- New commands: `task-master rules add <rules>` and `task-master rules remove <rules>` let you add or remove specific rules and MCP config after initialization, supporting multiple rules at once.
- New command: `task-master rules setup` launches an interactive prompt to select which rules to apply to your project. This does **not** re-initialize your project or affect shell aliases; it only manages rules. The list of rules is always up-to-date with available profiles, so you never have to update the CLI when adding a new rule set.
- The interactive rules setup flow is also used during `init` if you don't specify rules with `--rules`.
- Documentation and tests were updated to reflect these changes.
This enables more flexible, brand-specific project setups and makes rules management much easier. You can update or switch brands at any time after initialization using the interactive setup.
This enables more flexible, rule-specific project setups and makes rules management much easier. You can update or switch rules at any time after initialization using the interactive setup.
- Resolves #338