Git Worktree & Environment Manager FAQs

Question 1

How does the skill prevent port conflicts between worktrees?

Accepted Answer

The skill uses a deterministic port allocation strategy (base + stride) and persists these assignments in a .worktree-ports.json file. This ensures that every worktree gets its own unique set of ports for web servers, databases, and caches.

Question 2

Will I lose uncommitted changes during cleanup?

Accepted Answer

No. The cleanup utility includes built-in safety checks that detect 'dirty' worktrees with uncommitted files. It will skip these worktrees unless you explicitly use a force flag, preventing accidental data loss.

Question 3

Why should I use worktrees instead of just switching branches?

Accepted Answer

Git worktrees allow you to have multiple branches checked out at the same time in different directories. This lets you run different versions of your app simultaneously, avoid frequent stashing, and perform long-running tasks like dependency installs in the background without blocking your main workflow.

Question 4

Can this skill help with Docker-based projects?

Accepted Answer

Yes. It provides deterministic port maps that can be applied to docker-compose.worktree.yml files, allowing each worktree to spin up its own isolated container stack without host port collisions.

Git Worktree & Environment Manager

Key Features

Use Cases

Git Worktree & Environment Manager

Key Features

Use Cases