worktree-setup

Git worktrees isolate feature branches by creating separate working directories, allowing parallel feature development without filesystem interference. This skill automates worktree creation, handles reuse of existing worktrees, and safely falls back if directory issues arise.

Git worktrees are needed during PACT orchestrate and compact phases to maintain strict filesystem isolation for each feature branch. This skill automates worktree setup for these phases, ensuring parallel sub-scope execution does not overwrite or conflict with your main repository state.

Yes, you can reuse an existing git worktree. This skill checks for current worktrees and reuses the applicable directory instead of duplicating, while pruning stale worktree references to keep your repository configuration clean and accurate.

Setting up isolated git worktrees requires no external dependencies beyond standard Git tooling. This skill validates your repository structure, such as checking for the .worktrees directory, and automatically configures your gitignore to ensure worktrees are properly excluded from version tracking.

The best way to manage multiple isolated feature branches is using dedicated git worktrees. This skill automates the creation of a .worktrees directory, provides filesystem isolation for each branch, and reports the final path so you can immediately begin parallel development.