* 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
2.4 KiB
2.4 KiB
Update a single specific task with new information.
Arguments: $ARGUMENTS
Parse task ID and update details.
Single Task Update
Precisely update one task with AI assistance to maintain consistency.
Argument Parsing
Natural language updates:
- "5: add caching requirement"
- "update 5 to include error handling"
- "task 5 needs rate limiting"
- "5 change priority to high"
Execution
task-master update-task --id=<id> --prompt="<context>"
Update Types
1. Content Updates
- Enhance description
- Add requirements
- Clarify details
- Update acceptance criteria
2. Metadata Updates
- Change priority
- Adjust time estimates
- Update complexity
- Modify dependencies
3. Strategic Updates
- Revise approach
- Change test strategy
- Update implementation notes
- Adjust subtask needs
AI-Powered Updates
The AI:
-
Understands Context
- Reads current task state
- Identifies update intent
- Maintains consistency
- Preserves important info
-
Applies Changes
- Updates relevant fields
- Keeps style consistent
- Adds without removing
- Enhances clarity
-
Validates Results
- Checks coherence
- Verifies completeness
- Maintains relationships
- Suggests related updates
Example Updates
/project:tm/update/single 5: add rate limiting
→ Updating Task #5: "Implement API endpoints"
Current: Basic CRUD endpoints
Adding: Rate limiting requirements
Updated sections:
✓ Description: Added rate limiting mention
✓ Details: Added specific limits (100/min)
✓ Test Strategy: Added rate limit tests
✓ Complexity: Increased from 5 to 6
✓ Time Estimate: Increased by 2 hours
Suggestion: Also update task #6 (API Gateway) for consistency?
Smart Features
-
Incremental Updates
- Adds without overwriting
- Preserves work history
- Tracks what changed
- Shows diff view
-
Consistency Checks
- Related task alignment
- Subtask compatibility
- Dependency validity
- Timeline impact
-
Update History
- Timestamp changes
- Track who/what updated
- Reason for update
- Previous versions
Field-Specific Updates
Quick syntax for specific fields:
- "5 priority:high" → Update priority only
- "5 add-time:4h" → Add to time estimate
- "5 status:review" → Change status
- "5 depends:3,4" → Add dependencies
Post-Update
- Show updated task
- Highlight changes
- Check related tasks
- Update suggestions
- Timeline adjustments