How do I install the Git Worktree Manager skill?

Run npx skillmds@latest add droodotfoo/git-worktree-manager in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Git Worktree Manager safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Git Worktree Manager?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Git Worktree Manager free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Git Worktree Manager?

DROOdotFOO (@droodotfoo) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Git Worktree Manager by droodotfoo — Agent Skill

Name: Git Worktree Manager
Author: DROOdotFOO

Git Worktree Manager

Parallel development with git worktrees and deterministic port isolation. TRIGGER when: user wants to work on multiple branches simultaneously, run parallel agent sessions, manage worktree-based dev environments, or asks about port conflicts between concurrent services. DO NOT TRIGGER when: simple branch switching (use git checkout), or single-branch development with no parallelism needed.

DROOdotFOO e49bf77 2 files · 5.1 KB Updated Sep 17, 2026

File contents

git-worktree-manager

Parallel development using git worktrees with deterministic port allocation. Designed for multi-agent workflows where multiple branches run services concurrently without port collisions.

What You Get

Worktree lifecycle management (create, list, cleanup)
Deterministic port allocation with collision detection
Docker Compose patterns for per-worktree services
Decision matrix for when worktrees add value

Workflow

Decide -- Check the decision matrix below. Worktrees add overhead; use them only when parallelism is required.
Create -- git worktree add ../project-feature feature-branch
Allocate ports -- Use deterministic formula from port-allocation.md
Run sessions -- Each worktree gets isolated services on unique ports
Cleanup -- git worktree remove ../project-feature and release ports

Decision matrix

Situation	Use worktree?	Why
Quick fix while feature branch is running	Yes	Keep feature services up, fix on main
Multiple agents working different features	Yes	Each agent gets isolated environment
Long-running test suite on one branch	Yes	Continue development without waiting
Simple feature branch, no running services	No	git checkout is simpler
Reviewing a PR locally	Maybe	Only if your current branch has state
Shared database migrations in flight	No	Worktrees share .git; migrations collide

Rules

Never create worktrees inside the main working tree
Use sibling directories: ../project-feature, not ./worktrees/feature
Always allocate ports before starting services
Clean up worktrees when the branch is merged
Commit or stash before removing a worktree

Reading guide

Working on	Read
Port formula, collision checks, Docker Compose	port-allocation

---name: git-worktree-managerdescription: Parallel development with git worktrees and deterministic port isolation. TRIGGER when: user wants to work on multiple branches simultaneously, run parallel agent sessions, manage worktree-based dev environments, or asks about port conflicts between concurrent services. DO NOT TRIGGER when: simple branch switching (use git checkout), or single-branch development with no parallelism needed.---# git-worktree-managerParallel development using git worktrees with deterministic port allocation.Designed for multi-agent workflows where multiple branches run servicesconcurrently without port collisions.## What You Get- Worktree lifecycle management (create, list, cleanup)- Deterministic port allocation with collision detection- Docker Compose patterns for per-worktree services- Decision matrix for when worktrees add value## Workflow1. **Decide** -- Check the decision matrix below. Worktrees add overhead; use them only when parallelism is required.2. **Create** -- `git worktree add ../project-feature feature-branch`3. **Allocate ports** -- Use deterministic formula from port-allocation.md4. **Run sessions** -- Each worktree gets isolated services on unique ports5. **Cleanup** -- `git worktree remove ../project-feature` and release ports## Decision matrix| Situation | Use worktree? | Why || ------------------------------------------ | ------------- | ---------------------------------------- || Quick fix while feature branch is running | Yes | Keep feature services up, fix on main || Multiple agents working different features | Yes | Each agent gets isolated environment || Long-running test suite on one branch | Yes | Continue development without waiting || Simple feature branch, no running services | No | git checkout is simpler || Reviewing a PR locally | Maybe | Only if your current branch has state || Shared database migrations in flight | No | Worktrees share .git; migrations collide |## Rules1. Never create worktrees inside the main working tree2. Use sibling directories: `../project-feature`, not `./worktrees/feature`3. Always allocate ports before starting services4. Clean up worktrees when the branch is merged5. Commit or stash before removing a worktree## Reading guide| Working on | Read || ------------------------------------------------ | ------------------------------------------------- || Port formula, collision checks, Docker Compose | [port-allocation](port-allocation.md) |

Frequently asked questions