Files
claude-task-master/assets/claude/commands/tm/update/update-task.md
Joe Danziger 95c299df64 Unify and streamline profile system architecture (#853)
* 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
2025-07-09 13:22:11 +02:00

1.9 KiB

Update tasks with intelligent field detection and bulk operations.

Arguments: $ARGUMENTS

Intelligent Task Updates

Parse arguments to determine update intent and execute smartly.

1. Natural Language Processing

Understand update requests like:

  • "mark 23 as done" → Update status to done
  • "increase priority of 45" → Set priority to high
  • "add dependency on 12 to task 34" → Add dependency
  • "tasks 20-25 need review" → Bulk status update
  • "all API tasks high priority" → Pattern-based update

2. Smart Field Detection

Automatically detect what to update:

  • Status keywords: done, complete, start, pause, review
  • Priority changes: urgent, high, low, deprioritize
  • Dependency updates: depends on, blocks, after
  • Assignment: assign to, owner, responsible
  • Time: estimate, spent, deadline

3. Bulk Operations

Support for multiple task updates:

Examples:
- "complete tasks 12, 15, 18"
- "all pending auth tasks to in-progress"
- "increase priority for tasks blocking 45"
- "defer all documentation tasks"

4. Contextual Validation

Before updating, check:

  • Status transitions are valid
  • Dependencies don't create cycles
  • Priority changes make sense
  • Bulk updates won't break project flow

Show preview:

Update Preview:
─────────────────
Tasks to update: #23, #24, #25
Change: status → in-progress
Impact: Will unblock tasks #30, #31
Warning: Task #24 has unmet dependencies

5. Smart Suggestions

Based on update:

  • Completing task? → Show newly unblocked tasks
  • Changing priority? → Show impact on sprint
  • Adding dependency? → Check for conflicts
  • Bulk update? → Show summary of changes

6. Workflow Integration

After updates:

  • Auto-update dependent task states
  • Trigger status recalculation
  • Update sprint/milestone progress
  • Log changes with context

Result: Flexible, intelligent task updates with safety checks.