using-git-worktrees

Git worktrees let you create independent workspace copies linked to different branches, eliminating context switching. Set up a worktree by specifying a branch name and directory—the Skill auto-detects your project type, runs setup commands like `npm install` or `cargo build`, and verifies the baseline with tests, giving you a ready-to-use isolated environment.

Worktrees solve workspace conflicts by isolating each branch in its own directory, preventing accidental commits to the wrong branch. Instead of switching branches repeatedly, maintain parallel worktrees—one per feature—so you work cleanly on multiple features simultaneously without contaminating your current workspace.

Yes, the Skill auto-detects Node, Rust, Python, and Go projects and runs project-specific setup commands automatically. It installs dependencies, builds artifacts as needed, and runs baseline tests to ensure your worktree is functional before you start coding.

The Skill includes safety verification that checks `.gitignore` rules before creating worktrees, ensuring optimal directory placement. It respects your repository's structure and version control configuration, so worktrees integrate cleanly with existing ignore patterns and nested layouts.

Branch switching loses your working state, rebuild times are wasted, and you risk accidentally committing to the wrong branch. Worktrees keep your contexts completely separate—each branch has its own files, build artifacts, and state—so you switch projects instantly without interruption or cleanup.

Each worktree is a separate directory with its own working tree tied to a specific branch. You work in the correct directory for each feature, so Git commits automatically go to the intended branch—there's no risk of pushing changes to the wrong branch because you're working in isolated, branch-specific directories.