using-git-worktrees

To create an isolated git worktree, this skill uses priority-based directory selection to safely develop new features in a separate workspace without altering your main project, then automatically bootstraps project dependencies for a clean baseline.

Verifying your git worktree directory is ignored by Git prevents accidental commits of worktree contents into the main branch, ensuring safe experimentation and protecting your primary project workspace from unintended file tracking.

Yes, you can automatically bootstrap project dependencies for common stacks like Node, Rust, Python, and Go after creating a git worktree, executing baseline verification to ensure a clean, reproducible development environment before you start.

The best way to manage parallel development across git branches is using isolated worktrees, which allow you to safely experiment and test changes in separate directories without disrupting your main workspace or switching branches constantly.

Git worktree isolation works with existing local directories by applying priority-based selection that prefers an existing local worktree directory, then checks global preferences, and finally prompts the user to minimize workspace disruption.

You need a git worktree instead of a standard branch when starting feature work or experimentation that requires an isolated directory, allowing you to develop safely across parallel branches without disturbing your current working directory state.