worktree-parallel

Create and manage a git worktree for parallel feature development, then open the new worktree in the editor (code/Cursor) for a second Codex session. Use when the user asks to work on another feature simultaneously, spin up a parallel workspace, or open a new worktree even if they do not mention worktree explicitly.

Stars 163

Forks 31

Install this agent skill to your Project

npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/development/unknown-noah-rivard-news-coverage-a24-li

SKILL.md

Worktree Parallel

Workflow

Confirm the repo root (use current working directory unless the user specifies another repo).
Determine a feature slug and branch name.
- Default branch pattern: feat/<slug>.
- If the user already has a branch name, use it.
Choose a base directory for linked worktrees.
- Default for this repo: ../<project_name>-wt (create it if missing).
Create the worktree.
- New branch: git worktree add -b feat/<slug> <base>/<slug>
- Existing branch: git worktree add <base>/<slug> <branch>
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).
Suggest a parallel Codex session in the new worktree.
- cd <path> && codex
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>