using-git-worktrees

Git worktrees create separate working directories for different branches within the same repository, letting you work on multiple features simultaneously without switching contexts. This skill automates worktree creation with smart directory selection and safety checks to prevent repository pollution.

Isolated Git worktrees eliminate conflicts by giving each branch its own workspace. This skill sets up worktrees with automatic .gitignore verification and conditional project setup (npm, cargo, pip, go mod), ensuring clean isolation across your development workflow.

Yes. Git worktrees let you maintain separate working directories for different branches—work on your feature branch in one directory while keeping your bug fix branch active elsewhere. This skill handles directory prioritization, safety verification, and project-specific setup automatically.

When creating worktrees, this skill automatically checks and updates .gitignore entries to ensure project-local worktree directories aren't accidentally committed. It verifies safety before declaring the worktree ready for development.

Yes. This skill auto-detects your project type and conditionally sets up the appropriate dependency manager (npm, cargo, pip/poetry, go mod). It runs baseline tests across all project types to verify the worktree is ready before reporting success.

Worktrees preserve your full development environment for each branch—no stashing, no losing uncommitted work, no rebuilding dependencies. This skill automates the process with directory prioritization and safety checks, making context-free parallel development practical.