using-git-worktrees

Git worktrees create isolated branch-backed directories so you can develop multiple features in parallel without repeatedly switching branches in your main workspace. This prevents disrupting your current working state while keeping changes safely separated.

Git check-ignore validates that project-local worktree directories are ignored before creation, enforcing safety verification to reduce the risk of committing worktree artifacts. This ensures your isolated feature directories remain untracked by the repository.

Setting up an isolated git worktree involves smart directory selection that prefers existing .worktrees or worktrees folders, then checks CLAUDE.md for configured preferences, and otherwise prompts you for a location. Project setup and a clean baseline test pass are then executed automatically.

No manual configuration is required. Worktree directory selection prioritizes existing .worktrees directories first, then checks CLAUDE.md for a configured preference, and otherwise asks you directly where to create the worktree, ensuring flexible setup.

Running dependency installation and a clean baseline test pass in the new worktree verifies that the isolated environment is fully bootstrapped and ready. This confirms your feature work starts from a known-good state before implementation begins.

Yes, git worktrees are designed for preparing an agent-driven workspace for subsequent implementation steps. By creating an isolated worktree with validated ignore status and passing baseline tests, the environment is safe and ready for automated feature work.