Install
$ agentstack add skill-droodotfoo-agent-skills-git-worktree-manager ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
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-featureand 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](port-allocation.md) |
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: DROOdotFOO
- Source: DROOdotFOO/agent-skills
- License: MIT
- Homepage: https://droo.foo/
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.