worktree

<user_request> $ARGUMENTS </user_request>

Create a new worktree following the dev:worktree-lifecycle skill phases 1-5.

Steps:
1. If branch-name not provided, ask user for branch name
2. Use AskUserQuestion to ask for worktree directory (or use .worktrees/ default)
3. Execute Phase 1: Pre-flight Checks
   - Verify git repository
   - Check branch availability
   - Check path availability
4. Execute Phase 2: Directory Selection (use provided or ask)
5. Execute Phase 3: Creation
   - Verify .gitignore
   - Create worktree with `git worktree add`
   - Store original CWD
6. Execute Phase 4: Setup
   - Detect stacks (nodejs, rust, golang, python, ruby)
   - Install dependencies for each stack
   - Run baseline tests
7. Execute Phase 5: Handoff
   - Display worktree information
   - Show path, branch, stacks, test results
8. Write worktree context marker for statusline persistence
   - Get Claude Code session ID (if available from environment or session context)
   - Write marker file to `~/.claude/.statusline-worktree-{SESSION_ID}`:
     ```json
     {
       "worktree_path": ".worktrees/{slug}",
       "branch": "{branch-name}",
       "worktree_name": "{slug}"
     }
     ```
   - This marker survives context compaction and ensures the statusline
     continues showing worktree info after long-running operations

Output format:
```
Worktree created successfully!

Path: .worktrees/{slug}
Branch: {branch-name}
Stacks: {detected-stacks}
Tests: {passing} passing, {failing} failing

To work in this worktree:
  cd .worktrees/{slug}

To clean up later:
  /dev:worktree cleanup .worktrees/{slug}
```

Show all active worktrees in this repository.

Steps:
1. Run `git worktree list --porcelain`
2. Parse output to extract:
   - Worktree path
   - Branch name
   - HEAD commit
   - Locked status
3. Format as table:

```
Active Worktrees:

Path                          Branch              Commit
────────────────────────────────────────────────────────────
/path/to/project              main                abc1234
/path/to/.worktrees/feature   feature/auth        def5678
/path/to/.worktrees/hotfix    hotfix/login        ghi9012
```

If no worktrees besides main:
```
No additional worktrees found.
Only main worktree is active.

Create a worktree with: /dev:worktree create [branch-name]
```

Remove a worktree following dev:worktree-lifecycle Phase 6.

Steps:
1. If path not provided, list available worktrees and ask which to clean up
2. Execute Phase 6 cleanup:
   - Return to original CWD if currently in worktree
   - Check for uncommitted changes
   - If uncommitted changes:
     Use AskUserQuestion:
       question: "Uncommitted changes found. How to proceed?"
       options:
         - Commit now
         - Stash changes
         - Discard changes
         - Abort cleanup
   - Remove worktree with `git worktree remove`
   - Remove statusline worktree marker: `rm -f ~/.claude/.statusline-worktree-*`
     (clean all markers for this project to avoid stale files)
   - Optionally delete branch (only if merged)