Git Worktree Manager FAQs

Question 1

How does the skill handle repository organization?

Accepted Answer

It follows a best-practice pattern of storing worktrees in a hidden '.worktrees/' directory at your project root and ensures this directory is added to your .gitignore.

Question 2

Does this skill help with project setup in new worktrees?

Accepted Answer

Yes, it automatically detects project types and can run setup commands like yarn install, npm install, or pip install to ensure the new worktree is ready for use.

Question 3

Is it possible to work on the same branch in two different worktrees?

Accepted Answer

No, Git prevents a single branch from being checked out in multiple worktrees simultaneously to prevent data corruption; the skill helps you create new branches to avoid this.

Question 4

What is the primary benefit of using Git worktrees over stashing?

Accepted Answer

Git worktrees allow you to have multiple branches checked out at once in different directories, meaning you can switch tasks instantly without losing your uncommitted work or rebuild state.

Question 5

Can I use this skill to clean up merged branches?

Accepted Answer

Yes, the skill includes commands to safely remove worktrees, delete their associated branches, and prune any stale metadata from the Git repository.

Git Worktree Manager

소개

주요 기능

사용 사례

Git Worktree Manager

소개

주요 기능

사용 사례