Git Worktree Skill
Manage parallel development environments without manual path juggling.
When to Use
- Setting up parallel agents
- Multi-agent development
- When "worktree" is mentioned
- Need isolated environments for different features
Status Check
git worktree list
git branch --listActions
[NEW] Create Agent Environment
- Name the Agent: Short identifier (e.g.,
frontend-refactor,agent-3) - Define Paths:
- Branch: [agent-name] - Folder: ../[repo-name]-[agent-name]
- Execute:
git branch [branch_name]
git worktree add [folder_path] [branch_name]- Validate:
git worktree list - Context Migration (ask user):
cp .env [worktree_path]/.env
# If SQLite:
mkdir -p [worktree_path]/prisma
cp prisma/dev.db [worktree_path]/prisma/dev.db- Initialize:
pnpm installin new worktree
[SYNC] Synchronize Agents
- Ask: Sync ALL or SPECIFIC worktree?
- Execute:
git fetch origin
cd [worktree_path]
git merge origin/main # or rebase
cd -[KILL] Teardown Agent
- Select worktree from list
- Execute:
git worktree remove [worktree_path]
git branch -d [branch_name] # Ask before deleting!
git worktree pruneTroubleshooting
- "already checked out": Use a new branch name
- Stale entries: Run
git worktree prune - Files still tracked: Directory was deleted manually—prune first