Git Worktree Manager FAQs

Question 1

Why use sibling directories for worktrees instead of nesting them?

Accepted Answer

Nesting worktrees inside the main repo often causes issues with stale CLAUDE.md files and environment configurations. Sibling directories keep the main repo clean and isolated.

Question 2

Does it support Firebase service accounts?

Accepted Answer

Yes, it includes built-in logic to set the GOOGLE_APPLICATION_CREDENTIALS path in .env.local, pointing to your local Firebase service account key.

Question 3

How does it handle environment variables like .env files?

Accepted Answer

The skill automatically performs a recursive search and copy of .env files from the main repo to the worktree, ensuring the new environment is ready for development immediately.

Question 4

Is this skill safe for teams using multiple AI agents?

Accepted Answer

Yes, it is specifically designed for multi-agent environments by enforcing rules that prevent any agent from performing git operations like checkout or pull in the main repository.

Question 5

How do I clean up a worktree once a feature is merged?

Accepted Answer

The skill provides standardized commands to remove the worktree directory, delete the local branch, and prune stale git references to keep your workspace tidy.

Git Worktree Manager

Key Features

Use Cases

Git Worktree Manager

Key Features

Use Cases