using-git-worktrees

Git worktrees create isolated branches in separate directories, letting you develop multiple features simultaneously without switching contexts in your main workspace. Use `git worktree add .worktrees/feature-name -b feature-name` to create a new worktree, then navigate into it and run project setup commands.

Yes. Worktrees isolate feature work in dedicated directories so your primary checkout stays clean. The Skill enforces .gitignore safety checks to prevent accidental commits and auto-detects project dependencies to set up each worktree with a clean baseline.

No. The Skill auto-detects your project's build tooling (npm, cargo, pip, poetry, go) and installs dependencies automatically. It then runs baseline tests to verify the worktree is ready for development.

The Skill prioritizes `.worktrees` or `worktrees` directories if they exist, checks your CLAUDE.md preferences next, then falls back to global storage. Reusing existing worktree directories avoids duplication and keeps your repository organized.

Git worktrees work with any git repository. The Skill supports npm, cargo, pip, poetry, and go for automatic dependency installation. If your project uses a different tooling, you can still create worktrees manually and run setup commands yourself.

Worktree directories must be in .gitignore to prevent accidental commits of worktree contents into version control. The Skill verifies this safety check automatically before creating a new worktree.