using-git-worktrees

To create an isolated git worktree, you can use this skill to set up a dedicated directory for your feature branch. It automatically detects your project type, runs language-specific dependency setup, and executes tests to verify a clean baseline before you start coding.

Your git worktree directory appears in commits because it is not listed in your .gitignore file. This skill verifies project-local worktree directories are git-ignored and automatically adds and commits the ignore entry to prevent repository contamination.

The safest way to set up a git worktree is to use an existing .worktrees or worktrees directory while respecting project configuration preferences. This skill prioritizes safe directory selection, isolates feature work, and prompts you when the location is ambiguous.

Yes, you can use git worktrees to run parallel experiments across Node, Rust, Python, and Go projects. This skill auto-detects the project type, runs the appropriate dependency setup, and executes tests to confirm a clean starting state across all supported languages.

To prevent accidental commits when starting branch-based development, use an isolated git worktree. This skill separates your feature work from the current workspace and performs safety verification to ensure worktree contents are ignored by version control.

You do not need to manually configure environment setup after creating a git worktree for supported languages. This skill automates the process by detecting your project type, running language-specific dependency installations, and executing tests to confirm a clean baseline.