What problem does it solve? Working on multiple branches or running parallel agent sessions in a single checkout causes branch switching friction, staging races, and lost work. This Skill sets up isolated git worktrees so each feature or session gets its own working directory sharing one repository. ## Core Features & Use Cases - Systematic directory selection: Follows a priority order of existing .worktrees/ or worktrees/ directories, then CLAUDE.md preferences, then asks the user. - Safety verification: Confirms project-local worktree directories are gitignored before creation, and auto-detects project setup (npm, cargo, uv, poetry, pip, go) plus runs baseline tests. - Multi-session and recovery guidance: Covers worktree-per-actor isolation for concurrent agents, recovering vanished branches by checking origin/main, handling gitignored deliverables, and targeting correct absolute paths across worktrees. - Use Case: Before implementing an approved feature plan, create an isolated worktree at .worktrees/feature-auth, install dependencies, verify tests pass, and develop without disturbing the main checkout. ## Quick Start Use the using-git-worktrees skill to set up an isolated workspace for my new feature branch and verify the test baseline passes.
