using-git-worktrees

Git worktrees create isolated workspaces sharing the repository, allowing parallel feature work without disrupting the current directory. The skill prioritizes hidden .worktrees directories, then standard worktrees, then CLAUDE.md guidance, or prompts the user for a new location.

Git branch isolation across multiple projects is managed by auto-detecting project language and tooling like Node, Rust, Python, or Go, then running appropriate setup steps automatically to provide a reproducible baseline before implementation begins.

Git worktree paths need gitignore verification to prevent the new worktree directory from being accidentally tracked by the main repository. The skill verifies the path is ignored and applies Jesse's rule to fix issues if it is not ignored.

Global worktree locations are supported and bypass the standard gitignore safety verification checks. This allows you to create isolated git worktrees outside the repository directory structure entirely, preserving your current state without requiring local ignore rules.

Setting up git worktrees does not require manual configuration for each project. The skill automatically determines project location, reads CLAUDE.md preferences, detects project tooling, and provides an end-to-end workflow from project-name detection to clean baseline verification.