using-git-worktrees

Git worktrees create isolated workspaces sharing the same repository to prevent main workspace disruption. This Skill automates worktree creation on a new branch, applying safety checks to ensure clean baselines and ignored directory placement for parallel branch work.

Using git worktrees is the best way to manage parallel branches without context switching. The Skill isolates work by creating project-local or global worktrees, automatically detecting the project name and applying project-specific setup scripts when present.

The worktree creation process detects the project name automatically, creates the worktree on a new branch, and runs optional project-specific setup scripts. It follows a defined priority order for worktree placement to ensure environments are isolated correctly.

Yes, the worktree creation process includes safety checks to ensure worktrees are placed in ignored locations. This prevents the risk of accidentally committing worktree contents to the main repository and verifies clean baselines before starting feature work.

You should not use git worktrees when your project lacks ignored directories for safe placement, as the safety checks require clean baselines. If your project cannot support isolated environments or lacks defined priority paths, worktree creation may fail.