worktree

<user_request> $ARGUMENTS </user_request>

Create a new worktree following the 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 3.5: Database Branch (if applicable)
   - Detect database provider from .env (neon.tech, turso.io, supabase.co)
   - If branchable provider detected, ask user if branch involves schema changes
   - If yes: create DB branch, get connection string, patch .env, write .db-branch.json
   - Follow `${CLAUDE_PLUGIN_ROOT}/skills/backend/db-branching/SKILL.md` (read the
     file) for the provider-specific procedure
7. Execute Phase 4: Setup
   - Detect stacks (nodejs, rust, golang, python, ruby)
   - Install dependencies for each stack
   - If Neon branch created: run schema push command against branch
   - Run baseline tests
8. Execute Phase 5: Handoff
   - Display worktree information
   - Show path, branch, stacks, test results
   - If Neon branch: show Neon branch ID and isolation status

Output format:
```
Worktree created successfully!

Path: .worktrees/{slug}
Branch: {branch-name}
Stacks: {detected-stacks}
Tests: {passing} passing, {failing} failing
Neon Branch: {branch-id} (from {parent}) | (none)
Database: Isolated | Shared (production)

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. For each worktree, check for `.db-branch.json` to detect Neon branches
4. Format as table:

```
Active Worktrees:

Path                          Branch              Commit    Neon Branch
──────────────────────────────────────────────────────────────────────────
/path/to/project              main                abc1234   production
/path/to/.worktrees/feature   feature/auth        def5678   br-dark-sky-a8xyz123
/path/to/.worktrees/hotfix    hotfix/login        ghi9012   (none)
```

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 the worktree-lifecycle skill's 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
   - Check for `.db-branch.json` in worktree root
   - If database branch exists, follow the cleanup in
     `${CLAUDE_PLUGIN_ROOT}/skills/backend/db-branching/SKILL.md`:
     - Ask user about schema migration (apply to production / discard / keep)
     - If applying: merge code first, then run schema push in main worktree
     - Delete database branch via provider-specific method (MCP or CLI)
   - Remove worktree with `git worktree remove`
   - Optionally delete branch (only if merged)