using-git-worktrees

Git worktrees isolate feature work by creating dedicated directories that share the same repository, preventing accidental changes to your main workspace. This Skill automates directory selection, safety verification, and project setup.

An isolated development workflow benefits from using git worktrees to separate feature branches physically. This approach applies priority rules—local directory first, then CLAUDE.md preferences, then user prompts—to automate worktree creation and baseline verification.

Automating project setup during git worktree creation involves running setup commands defined in project files immediately after the worktree is initialized. This ensures the new isolated environment is fully prepared and reports readiness for feature work.

Yes, git worktree creation validates gitignore configurations as part of its safety verification process. This step ensures the isolated work area remains separate and prevents unintended changes from leaking into the main repository.

Yes, you can use a local worktree directory preference first. The workflow imposes priority rules: it checks local configurations initially, then CLAUDE.md preferences, and finally falls back to user prompts for directory selection.

Git worktrees may not suit feature isolation if your project lacks standard setup files for automated baseline verification, or if physical directory separation creates conflicts with your existing development workflow and tooling configurations.