using-git-worktrees

Git worktrees let you create isolated working directories for different branches from the same repository. Each worktree is a separate filesystem directory linked to your Git repo, so you can work on multiple features in parallel without stashing or switching branches.

Create a worktree with `git worktree add .worktrees/feature-name -b feature/name`, then the Skill automatically runs project setup—npm install, cargo build, pip install, or poetry install—and baseline tests to verify readiness before you start coding.

Yes. Worktrees isolate feature work in separate directories so your main branch remains untouched. You develop in the worktree, test independently, and merge only when ready—eliminating context switching and incomplete work conflicts.

The Skill handles directory selection automatically by checking project-local paths (.worktrees or worktrees) first, then global (~/.config/worktrees) if needed. It respects .gitignore safety rules to avoid storing worktrees in ignored locations.

No. The Skill runs environment setup automatically after creating the worktree—detecting your project type and executing npm install, cargo build, pip/poetry install, or go mod download—then validates with baseline tests.