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
108 lines
2.4 KiB
Markdown
108 lines
2.4 KiB
Markdown
Update multiple tasks starting from a specific ID.
|
|
|
|
Arguments: $ARGUMENTS
|
|
|
|
Parse starting task ID and update context.
|
|
|
|
## Bulk Task Updates
|
|
|
|
Update multiple related tasks based on new requirements or context changes.
|
|
|
|
## Argument Parsing
|
|
|
|
- "from 5: add security requirements"
|
|
- "5 onwards: update API endpoints"
|
|
- "starting at 5: change to use new framework"
|
|
|
|
## Execution
|
|
|
|
```bash
|
|
task-master update --from=<id> --prompt="<context>"
|
|
```
|
|
|
|
## Update Process
|
|
|
|
### 1. **Task Selection**
|
|
Starting from specified ID:
|
|
- Include the task itself
|
|
- Include all dependent tasks
|
|
- Include related subtasks
|
|
- Smart boundary detection
|
|
|
|
### 2. **Context Application**
|
|
AI analyzes the update context and:
|
|
- Identifies what needs changing
|
|
- Maintains consistency
|
|
- Preserves completed work
|
|
- Updates related information
|
|
|
|
### 3. **Intelligent Updates**
|
|
- Modify descriptions appropriately
|
|
- Update test strategies
|
|
- Adjust time estimates
|
|
- Revise dependencies if needed
|
|
|
|
## Smart Features
|
|
|
|
1. **Scope Detection**
|
|
- Find natural task groupings
|
|
- Identify related features
|
|
- Stop at logical boundaries
|
|
- Avoid over-updating
|
|
|
|
2. **Consistency Maintenance**
|
|
- Keep naming conventions
|
|
- Preserve relationships
|
|
- Update cross-references
|
|
- Maintain task flow
|
|
|
|
3. **Change Preview**
|
|
```
|
|
Bulk Update Preview
|
|
━━━━━━━━━━━━━━━━━━
|
|
Starting from: Task #5
|
|
Tasks to update: 8 tasks + 12 subtasks
|
|
|
|
Context: "add security requirements"
|
|
|
|
Changes will include:
|
|
- Add security sections to descriptions
|
|
- Update test strategies for security
|
|
- Add security-related subtasks where needed
|
|
- Adjust time estimates (+20% average)
|
|
|
|
Continue? (y/n)
|
|
```
|
|
|
|
## Example Updates
|
|
|
|
```
|
|
/project:tm/update/from-id 5: change database to PostgreSQL
|
|
→ Analyzing impact starting from task #5
|
|
→ Found 6 related tasks to update
|
|
→ Updates will maintain consistency
|
|
→ Preview changes? (y/n)
|
|
|
|
Applied updates:
|
|
✓ Task #5: Updated connection logic references
|
|
✓ Task #6: Changed migration approach
|
|
✓ Task #7: Updated query syntax notes
|
|
✓ Task #8: Revised testing strategy
|
|
✓ Task #9: Updated deployment steps
|
|
✓ Task #12: Changed backup procedures
|
|
```
|
|
|
|
## Safety Features
|
|
|
|
- Preview all changes
|
|
- Selective confirmation
|
|
- Rollback capability
|
|
- Change logging
|
|
- Validation checks
|
|
|
|
## Post-Update
|
|
|
|
- Summary of changes
|
|
- Consistency verification
|
|
- Suggest review tasks
|
|
- Update timeline if needed |