Worktree Manager
Git worktree management with safe defaults and flexible placement strategies. Use when users ask to: (1) create a new worktree or work on multiple branches in parallel, (2) list existing worktrees, (3) remove or clean up worktrees, (4) manage worktree placement (subfolder vs sibling directory), or any other git worktree operations.
Install
$ agentstack add skill-jamesyorke-worktree-agent-skill-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.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-jamesyorke-worktree-agent-skill-worktree-manager) 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
Worktree Manager
Fast, interactive management of git worktrees with consistent conventions and automatic housekeeping.
Agent behavior contract
- Always use
--forcewhen removing worktrees — repos with submodules will fail without it. - Always run
git worktree pruneafter removing a worktree to clean up stale references. - When creating subfolder worktrees, ensure
.worktrees/is in.gitignorebefore creating. - Never hardcode worktree paths in remove operations — always read from
git worktree list. - Default to subfolder placement unless the user explicitly chooses parent folder.
- Default the worktree folder name to the last segment of the branch name.
Triage (detect action)
If the user provided an argument (create, list, or remove), use that action. If no argument was provided, ask the user which action they want:
- create — Create a new worktree with a new branch
- list — List all current worktrees
- remove — Remove an existing worktree
Then read the appropriate reference:
Routing map
- Creating a worktree →
references/creating.md - Listing worktrees →
references/listing.md - Removing a worktree →
references/removing.md - Placement strategies & conventions →
references/placement.md - Common issues & troubleshooting →
references/troubleshooting.md
Common errors → next best move
- "working trees containing submodules cannot be moved or removed" → use
--forceflag (seereferences/removing.md) - Stale worktree references after manual deletion → run
git worktree prune(seereferences/removing.md) - Branch already checked out in another worktree → list worktrees to find which one, remove or use a different branch
.worktrees/showing up in git status → add to.gitignore(seereferences/placement.md)
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: jamesyorke
- Source: jamesyorke/worktree-agent-skill
- License: MIT
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.