using-git-worktrees

Git worktrees isolate feature development by automatically creating separate working directories, verifying gitignore rules to ensure a clean baseline for concurrent branch work without altering the main workspace.

Git worktree directory selection follows priority rules, preferring .worktrees then worktrees directories, while automatically applying user-specified paths from CLAUDE.md to ensure deterministic workspace locations without prompts.

Yes, gitignore verification is required before creating a git worktree because the skill enforces safety checks to ensure worktree directories are ignored locally and globally, preventing accidental repository commits.

Yes, environment setup commands for common toolchains run after git worktree creation because the guided workflow detects the project name, sets the path, and performs optional cross-tool setup to establish a clean baseline.

Using isolated git worktrees is the best way to manage parallel bugfix work across multiple branches, preserving a clean baseline and enabling concurrent development without the context switching overhead of a single workspace.

Git worktrees prevent context switching in the main workspace by creating isolated directories for parallel work, ensuring experiments and feature development run concurrently while preserving a clean, reproducible baseline.