using-git-worktrees

Isolated git worktrees separate feature work from the main workspace, preventing accidental cross-branch changes. This Skill automates directory discovery in project-local or global locations, applies gitignore safety verification, and executes onboarding steps to prepare the environment for parallel branch work without switching contexts.

Git worktrees allow you to manage multiple branches simultaneously by creating isolated working directories from a single repository. Each worktree maintains its own working directory state, enabling parallel development and experimentation without stashing or committing incomplete changes in your main workspace.

Worktree isolation enforces safety by verifying the chosen storage directory is properly ignored by gitignore rules before creation. This prevents the version control system from tracking the worktree location as an untracked path, ensuring temporary or parallel development directories are never accidentally committed.

Yes, git worktree storage locations can be configured using CLAUDE.md preferences. The automation prioritizes project-local directories like .worktrees, with a global fallback option, applying directory discovery logic to find existing worktree locations and matching them to your defined configuration preferences.

Isolated git worktrees are ideal for early feature development, experimentation, or parallel branch work on local or global locations. They share the same underlying repository history, avoiding the disk space overhead and remote synchronization required by a full repository clone for isolated feature work.