using-git-worktrees

Creating a git worktree for feature development isolates your changes by setting up a separate working directory. This skill selects an appropriate local or global location, applies safety checks, and verifies a clean baseline before handing off the new worktree.

Managing multiple git branches for parallel experimentation is best done using isolated git worktrees. This approach assigns each feature branch its own directory, preventing workspace pollution and allowing you to safely develop features concurrently.

Git check-ignore verifies worktree safety by ensuring the new worktree directory is properly ignored by your repository configuration. This prevents the contents of your isolated worktree from being accidentally committed to the main project.

You can use a global directory location for project worktrees instead of local folders. This skill supports flexible storage options, automatically inferring the project name and applying priority-based directory selection to find the right fit.

You need a clean git baseline before setting up an isolated worktree to ensure your main branch has no uncommitted changes. This skill validates your working directory state and reads CLAUDE.md preferences before creating the new worktree.