Git Worktree Manager FAQs

Question 1

What is the benefit of using Git worktrees over standard branching?

Accepted Answer

Git worktrees allow you to have multiple branches checked out at the same time in different directories. This eliminates the need to stash changes or perform frequent checkouts when switching between tasks.

Question 2

Does it automatically resolve branch names from issue numbers?

Accepted Answer

Yes, by providing a GitHub issue number, the skill uses internal scripts to resolve the appropriate branch name and directory structure automatically.

Question 3

How does this skill handle uncommitted work?

Accepted Answer

The skill includes a safety hook that detects uncommitted or unstaged changes. It will block the creation of a new worktree until you have committed or stashed your current work to ensure environment stability.

Question 4

Can I customize where my worktrees are stored?

Accepted Answer

Yes, the skill reads the WORKTREE_DIR variable from your .env.claude file. If not set, it will prompt you to define a preferred location for your worktree directories.

Question 5

How do I remove a worktree when I'm finished?

Accepted Answer

You can use the /devops:worktree remove <name> command, which checks for unpushed commits before safely deleting the worktree directory and optionally removing the associated branch.

Git Worktree Manager

主要功能

使用场景

Git Worktree Manager

主要功能

使用场景