using-git-worktrees

To isolate feature work with Git worktrees, create a separate directory using `git worktree add -b`. This prevents conflicts and accidental commits in your main working directory while keeping branch state independent.

The safest way to set up a Git worktree is to use a project-local directory like `.worktrees/` and verify it is ignored with `git check-ignore`. This prevents the worktree files from being accidentally tracked by Git.

To validate a clean test baseline in a new Git worktree, automatically run project setup commands like npm or cargo, then execute the project's test command to confirm the workspace starts in a good state before implementation.

Yes, dependency setup can run automatically when adding a Git worktree by detecting project files like package.json or Cargo.toml. This ensures the isolated workspace has all required dependencies installed before you begin feature work.

You should use Git worktrees instead of switching branches when you need isolated workspaces for long-running features. This approach avoids messy state and conflicts that often occur when managing multiple branches in a single working directory.

Your project-local worktree directory needs to be ignored by Git to prevent accidental tracking of nested repository files. Verifying ignore status with `git check-ignore` ensures the worktree remains a safe, isolated workspace.