majiayu000/claude-skill-registry-data/worktree-parallel-noah-rivard-news-coverage-a24-li

Worktree Parallel

Workflow

1. Confirm the repo root (use current working directory unless the user specifies another repo).
2. Determine a feature slug and branch name.

• Default branch pattern: feat/<slug>.
• If the user already has a branch name, use it.

1. Choose a base directory for linked worktrees.

• Default for this repo: ../<project_name>-wt (create it if missing).

1. Create the worktree.

• New branch: git worktree add -b feat/<slug> <base>/<slug>
• Existing branch: git worktree add <base>/<slug> <branch>

1. Open the worktree in the editor.

• Use code -n <path> (Cursor supports the code CLI).
• If code is unavailable, ask for the preferred editor command (e.g., cursor -n, code, or another).

1. Suggest a parallel Codex session in the new worktree.

• cd <path> && codex

1. Confirm with git worktree list if needed.

Safety

• Do not use --force unless the user explicitly asks.
• Do not remove existing worktrees unless the user requests cleanup.

Optional Cleanup (only if asked)

• git worktree remove <path>
• git branch -d <branch>