using-git-worktrees

Git worktrees create isolated working directories linked to the same repository, enabling safe feature development and experimentation without polluting the primary branch. This skill automates creating that isolated workspace and sets up a new branch.

Using git worktrees is the best way to manage multiple branches, as it creates separate directory instances for each feature. This prevents partial changes from interfering with your primary workspace while sharing the same repository history.

Yes, the worktree creation process respects existing project conventions by verifying local .gitignore rules and checking CLAUDE.md preferences to select an appropriate directory location for the isolated workspace.

To set up a git worktree, this skill auto-detects the project name, selects an appropriate directory, creates the worktree with a new branch, and runs optional lightweight setup steps to bring the workspace to a usable baseline.

You should use git worktrees instead of cloning when you need safe isolation for feature work or experiments within a single repository, avoiding the disk space overhead and separate history management required by a full clone.