using-git-worktrees

Git worktrees let you create separate working directories for different branches without switching contexts in your main workspace. This skill automates worktree setup, automatically selecting a safe directory, verifying .gitignore rules, installing dependencies, and running baseline tests so you can start coding immediately.

Worktrees eliminate context-switching overhead and keep your main branch pristine. Each worktree is an isolated workspace for a single branch, so you avoid uncommitted changes, stale dependencies, or accidental commits when toggling between features.

Yes. The skill auto-detects your project type, installs dependencies based on project files (package.json, Gemfile, etc.), and validates tests to ensure a clean baseline before you begin work.

It uses priority-based directory selection: first checks for a .worktrees directory, then worktrees, then respects CLAUDE.md preferences, and finally prompts for your choice. This ensures worktrees stay organized and follow project conventions.

The skill verifies and updates your .gitignore to prevent accidental commits of worktree content, enforces directory priority rules, and validates tests to confirm a working baseline state before isolation begins.

Yes. Each worktree is independent, so you can create separate isolated workspaces for multiple feature branches, bug fixes, or experiments simultaneously without affecting your main repository state.