using-git-worktrees

Creating an isolated git worktree involves choosing a safe directory location, verifying project gitignore rules, and checking out the target feature branch separately to prevent conflicts with your current workspace.

The safest way to set up a git workspace is enforcing gitignore rules for project-local worktree directories, verifying existing paths, and checking CLAUDE.md preferences before creating the isolated branch.

Git worktrees prevent repository pollution by verifying that project-local worktree directories are explicitly ignored by Git before creating any new isolated workspaces for parallel branch development.

Yes, you can run baseline tests automatically after setting up a git worktree. The skill configures dependencies and executes the project's test suite to validate workspace readiness before implementation begins.

You do not need to manually choose a directory location for your git worktree. The skill smartly selects an existing `.worktrees/` directory or checks project guidance before prompting you.

A key limitation of project-local worktrees is the risk of repository pollution if the worktree directory is not properly ignored by Git, which the skill mitigates by enforcing strict gitignore safety checks.