using-git-worktrees

To create a Git worktree for isolated feature branch work, this skill automates branch creation and directory selection, preferring project-local hidden directories like .worktrees while respecting CLAUDE.md preferences. It prepares the environment so changes do not bleed into the main workspace.

Managing Git worktrees safely requires isolating feature work in a separate directory. This skill selects a project-local or global location, verifies gitignore rules to prevent tracking, and automatically configures the environment for Node.js, Python, Go, or Rust projects.

Yes, Git worktree setup works with Node.js, Python, Go, and Rust projects. The skill auto-detects repository contents and prepares the environment by running the appropriate setup steps for the detected language, ensuring the isolated worktree is ready for development.

To ensure your Git worktree is ignored, this skill enforces safety verification by checking gitignore rules for project-local setups. If the worktree directory is not ignored, it automatically updates .gitignore to prevent the isolated worktree from being tracked in version control.

Yes, you can use a global location instead of a project-local Git worktree directory. When directory choice is ambiguous, the skill prompts the user, respecting CLAUDE.md preferences and supporting global worktree locations outside the repository to maintain isolation.

You should not use a project-local Git worktree setup if your .gitignore cannot be modified or if the directory structure prevents ignoring the worktree. In these cases, choosing a global worktree location outside the repository provides the necessary isolation without tracking conflicts.