using-git-worktrees

To create an isolated git worktree, the skill selects a project-local directory, verifies it is git-ignored, creates a new branch worktree, runs project setup commands, and executes tests to confirm a clean baseline before you begin implementation.

Git worktree workspace isolation creates separate working directories for different branches, preventing cross-branch workspace contamination. You need it when running parallel branches or starting feature work to avoid mixing changes with your main working tree.

To prevent accidental commits of worktree files, the skill verifies that project-local worktree directories are listed in gitignore. If the directory is not ignored, it automatically adds the ignore entry and commits the safety change.

Yes, you can run project setup and test validation automatically. After creating a new branch worktree, the skill runs dependency installations like npm install or cargo build and executes tests to verify a clean baseline before development begins.

Git worktree creation works with multiple project setup tools. The skill automatically detects and runs appropriate setup commands including npm install, cargo build, pip or poetry installations, and go mod commands to prepare the isolated workspace environment.

The best way to manage directory selection for git worktrees is using prioritized locations. The skill prefers a .worktrees directory, then a worktrees directory, respects CLAUDE.md preferences, and prompts the user when the location is ambiguous.