95c299df64
* move claude rules and commands to assets/claude * update claude profile to copy assets/claude to .claude * fix formatting * feat(profiles): Implement unified profile system - Convert Claude and Codex profiles to use createProfile() factory - Remove simple vs complex profile distinction in rule transformer - Unify convertAllRulesToProfileRules() to handle all profiles consistently - Fix mcpConfigPath construction in base-profile.js for null mcpConfigName - Update terminology from 'simpleProfiles' to 'assetOnlyProfiles' throughout - Ensure Claude .claude directory copying works in both CLI and MCP contexts - All profiles now follow same execution flow with proper lifecycle functions Changes: - src/profiles/claude.js: Convert to createProfile() factory pattern - src/profiles/codex.js: Convert to createProfile() factory pattern - src/utils/rule-transformer.js: Unified profile handling logic - src/utils/profiles.js: Remove simple profile categorization - src/profiles/base-profile.js: Fix mcpConfigPath construction - scripts/modules/commands.js: Update variable naming - tests/: Update all tests for unified system and terminology Fixes Claude profile asset copying issue in MCP context. All tests passing (617 passed, 11 skipped). * re-checkin claude files * fix formatting * chore: clean up test Claude rules files * chore: add changeset for unified profile system * add claude files back * add changeset * restore proper gitignore * remove claude agents file from root * remove incorrect doc * simplify profiles and update tests * update changeset * update changeset * remove profile specific code * streamline profiles with defaults and update tests * update changeset * add newline at end of gitignore * restore changes * streamline profiles with defaults; update tests and add vscode test * update rule profile tests * update wording for clearer profile management * refactor and clarify terminology * use original projectRoot var name * revert param desc * use updated claude assets from neno * add "YOUR_" before api key here * streamline codex profile * add gemini profile * update gemini profile * update tests * relocate function * update rules interactive setup Gemini desc * remove duplicative code * add comma
62 lines
1.3 KiB
Markdown
62 lines
1.3 KiB
Markdown
Remove a dependency between tasks.
|
|
|
|
Arguments: $ARGUMENTS
|
|
|
|
Parse the task IDs to remove dependency relationship.
|
|
|
|
## Removing Dependencies
|
|
|
|
Removes a dependency relationship, potentially unblocking tasks.
|
|
|
|
## Argument Parsing
|
|
|
|
Parse natural language or IDs:
|
|
- "remove dependency between 5 and 3"
|
|
- "5 no longer needs 3"
|
|
- "unblock 5 from 3"
|
|
- "5 3" → remove dependency of 5 on 3
|
|
|
|
## Execution
|
|
|
|
```bash
|
|
task-master remove-dependency --id=<task-id> --depends-on=<dependency-id>
|
|
```
|
|
|
|
## Pre-Removal Checks
|
|
|
|
1. **Verify dependency exists**
|
|
2. **Check impact on task flow**
|
|
3. **Warn if it breaks logical sequence**
|
|
4. **Show what will be unblocked**
|
|
|
|
## Smart Analysis
|
|
|
|
Before removing:
|
|
- Show why dependency might have existed
|
|
- Check if removal makes tasks executable
|
|
- Verify no critical path disruption
|
|
- Suggest alternative dependencies
|
|
|
|
## Post-Removal
|
|
|
|
After removing:
|
|
1. Show updated task status
|
|
2. List newly unblocked tasks
|
|
3. Update project timeline
|
|
4. Suggest next actions
|
|
|
|
## Safety Features
|
|
|
|
- Confirm if removing critical dependency
|
|
- Show tasks that become immediately actionable
|
|
- Warn about potential issues
|
|
- Keep removal history
|
|
|
|
## Example
|
|
|
|
```
|
|
/project:tm/remove-dependency 5 from 3
|
|
→ Removed: Task #5 no longer depends on #3
|
|
→ Task #5 is now UNBLOCKED and ready to start
|
|
→ Warning: Consider if #5 still needs #2 completed first
|
|
``` |