Git Worktree Manager FAQs

Question 1

Why should I use Git worktrees instead of git checkout?

Accepted Answer

Git worktrees allow you to have multiple branches checked out simultaneously in different folders. This means you can work on a new feature while keeping your main branch or other features open and running in separate terminal windows.

Question 2

Where are the new worktrees created?

Accepted Answer

By default, it creates worktrees in a sibling directory named '../pierre_mcp_server-[branch-name]', keeping your workspace organized.

Question 3

What environment files does this skill copy?

Accepted Answer

The skill is configured to copy .envrc and .mcp.json files from your main directory to the new worktree to ensure your environment variables and MCP settings are preserved.

Question 4

Does it handle direnv authorization automatically?

Accepted Answer

Yes, after creating the worktree and copying the environment files, it automatically runs 'direnv allow' in the new directory to activate your shell environment.

Question 5

How do I clean up a worktree when I am finished?

Accepted Answer

You can use 'git worktree remove' followed by the path to the directory, and then delete the branch using 'git branch -d'. This skill is also designed to pair with the 'finish-worktree' skill.

Git Worktree Manager

Key Features

Use Cases

Git Worktree Manager

Key Features

Use Cases