using-git-worktrees

To create an isolated git worktree, the skill detects your project name and runs git worktree add -b to generate a new branch directory. It verifies a clean baseline before coding to prevent main repository contamination.

Git worktree isolation is used to separate feature work, experimentation, or parallel tasks from the main repository. By creating dedicated worktrees, you prevent side effects and contamination during branch-based development.

Yes, when creating a git worktree, the workflow optionally runs project setup commands after adding the branch. This ensures the isolated directory is fully prepared and ready for coding without affecting the main repository.

Git worktree creation validates ignore rules to provide a deterministic and safe workflow. This ensures the isolated feature work environment has a clean baseline and follows safe defaults before any coding begins.

The best way to manage parallel tasks is creating isolated git worktrees. This approach separates feature work into dedicated directories using git worktree add -b, ensuring a clean baseline and preventing side effects on the main repository.

You should avoid git worktrees if your project lacks clearly defined directory priorities or cannot run project setup commands in isolation. Worktrees require verifying a clean baseline, which may disrupt workflows dependent on the main repository state.