using-git-worktrees

You create an isolated git worktree by using deterministic directory selection rules, verifying .gitignore entries, auto-detecting toolchain setup commands, and running baseline tests to ensure a clean environment.

Git worktrees allow you to run parallel development by creating isolated directories for separate feature branches, preventing cross-contamination between your primary working tree and new implementation tasks.

Git worktree isolation prevents accidental commits and environment contamination by standardizing directory locations and enforcing .gitignore verification, ensuring project-local worktree paths are properly ignored and committed before development begins.

Yes, git worktree creation auto-detects Node, Rust, Python, and Go toolchains, automatically running the appropriate dependency setup commands and verifying a clean test baseline before confirming environment readiness.

You need to verify .gitignore before creating a project-local git worktree to prevent the isolated directory from being tracked by version control, and this Skill automatically commits the fix if the entry is missing.

You should avoid git worktrees when your project lacks clear directory selection preferences or when automated toolchain detection and baseline test verification are unavailable, as these safety checks are required for a clean environment.