using-git-worktrees

To create an isolated Git workspace, the skill sets up a linked worktree using native tools or a manual fallback, ensuring your main branch is protected from churn. It selects a safe directory, installs dependencies, and runs baseline tests.

Preventing accidental changes involves working in a separate Git worktree rather than directly in your main checkout. This skill detects existing isolation and creates a new worktree only when needed, verifying ignore rules and a clean test baseline.

Dependency installation issues after switching branches often stem from conflicting project states. This skill resolves this by setting up an isolated worktree and automatically running dependency installation to ensure the new workspace starts with a clean state.

Yes, detecting existing isolation is a core feature. It safely determines whether you are already inside a linked worktree and avoids creating nested or duplicate isolation, preventing phantom state and directory conflicts.

Yes, the skill prefers platform- or harness-provided worktree creation mechanisms to avoid phantom state. It only falls back to manual git worktree commands with guardrails when native tooling is unavailable.

Verifying project-local ignore rules is necessary when creating a manual Git worktree to ensure the new directory is not accidentally committed. This skill automatically checks ignore rules during safe directory selection.