Git Worktree Manager FAQs

Question 1

Where does this skill store new worktrees?

Accepted Answer

The skill defaults to a sibling directory (../worktrees/) to avoid repository conflicts, but it can be configured via CLAUDE.md to store them inside a hidden '.worktrees/' folder within your project.

Question 2

Does this skill help with merge conflicts?

Accepted Answer

By isolating tasks in worktrees, you avoid the accidental conflicts that occur when switching branches with uncommitted changes. It also provides a structured way to merge worktree branches back into your main branch once tasks are finished.

Question 3

What is a Git worktree and why should I use one?

Accepted Answer

A Git worktree allows you to have multiple working directories attached to the same repository. This lets you work on different branches at the same time in separate folders, which is faster and safer than constantly stashing and switching branches.

Question 4

Is it safe to delete worktrees using this skill?

Accepted Answer

Yes, the skill implements safety checks to ensure your current working directory is not inside the worktree being deleted, preventing common shell errors and environment instability.

Question 5

How does the skill handle worktree cleanup?

Accepted Answer

It includes specific operations to list all active worktrees, prune stale references, and automatically identify and remove worktree directories that haven't been modified in over seven days.

Git Worktree Manager

Git Worktree Manager

Key Features

Use Cases

Key Features

Use Cases