How do I install the 1716 Worktree Guide 43d9a9da skill?

Run npx skillmds@latest add tools-only/1716-worktree-guide-43d9a9da 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.

What does the 1716 Worktree Guide 43d9a9da skill do?

Parallel Agent Isolation (Git Worktrees) It is listed under AI & ML on SkillMD.

Is 1716 Worktree Guide 43d9a9da 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 1716 Worktree Guide 43d9a9da?

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 1716 Worktree Guide 43d9a9da free to use?

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

Who published 1716 Worktree Guide 43d9a9da?

tools-only (@tools-only) published this skill. Their other Agent Skills are listed on their SkillMD profile.

1716 Worktree Guide 43d9a9da by tools-only

Name: 1716 Worktree Guide 43d9a9da
Author: tools-only

File contents

Parallel Agent Isolation (Git Worktrees)

When running multiple agents in parallel, each agent should use its own git worktree to avoid conflicts on git operations, checkpoint files, and version tracking.

Why Worktrees?

Without isolation, parallel agents cause:

Race conditions on git commit/git push
Checkpoint invalidation chaos (Agent A's version invalidated by Agent B's commit)
Silent merge conflicts when editing same files

Worktree Workflow

COORDINATOR (main repo)
├── Creates worktrees for each agent
├── Each agent diagnoses/fixes independently
├── Sequential merge after completion
└── Single deployment after merge

AGENT WORKTREE
├── Own branch: claude-agent/{agent-id}
├── Own .claude/ directory (checkpoint, state)
├── Independent log collection
└── Independent version tracking

Creating a Worktree

python3 ~/.claude/hooks/worktree-manager.py create <agent-id>
# Returns: /tmp/claude-worktrees/<agent-id>

Merging Agent Work

python3 ~/.claude/hooks/worktree-manager.py merge <agent-id>
# If conflict (exit code 2): fall back to sequential execution
python3 ~/.claude/hooks/worktree-manager.py cleanup <agent-id>

Coordinator Deploy Pattern

ONLY the coordinator deploys. Subagents NEVER deploy.

1. Create worktrees for each agent
2. Spawn Tasks (each gets worktree path in prompt)
3. Wait for all Tasks
4. Sequential merge (abort on conflict → fall back to sequential)
5. SINGLE deploy (coordinator only): git push && gh workflow run && gh run watch
6. Cleanup worktrees

SUBAGENT RULES (enforced by state file):

If coordinator: false, NEVER run gh workflow run or git push
Commit locally in worktree only
Mark needs_deploy: true in checkpoint

Coordination detection:

Skills set coordinator: false, parallel_mode: true in worktree autonomous-state.json
deploy-enforcer.py blocks subagent deploy attempts

Garbage Collection

python3 ~/.claude/hooks/worktree-manager.py gc           # Default 8-hour TTL
python3 ~/.claude/hooks/worktree-manager.py gc --dry-run # Preview cleanup

---name: 1716-worktree-guide-43d9a9dadescription: Parallel Agent Isolation (Git Worktrees)---# Parallel Agent Isolation (Git Worktrees)When running multiple agents in parallel, each agent should use its own **git worktree** to avoid conflicts on git operations, checkpoint files, and version tracking.## Why Worktrees?Without isolation, parallel agents cause:- Race conditions on `git commit`/`git push`- Checkpoint invalidation chaos (Agent A's version invalidated by Agent B's commit)- Silent merge conflicts when editing same files## Worktree Workflow```COORDINATOR (main repo)├── Creates worktrees for each agent├── Each agent diagnoses/fixes independently├── Sequential merge after completion└── Single deployment after mergeAGENT WORKTREE├── Own branch: claude-agent/{agent-id}├── Own .claude/ directory (checkpoint, state)├── Independent log collection└── Independent version tracking```## Creating a Worktree```bashpython3 ~/.claude/hooks/worktree-manager.py create <agent-id># Returns: /tmp/claude-worktrees/<agent-id>```## Merging Agent Work```bashpython3 ~/.claude/hooks/worktree-manager.py merge <agent-id># If conflict (exit code 2): fall back to sequential executionpython3 ~/.claude/hooks/worktree-manager.py cleanup <agent-id>```## Coordinator Deploy Pattern**ONLY the coordinator deploys. Subagents NEVER deploy.**```1. Create worktrees for each agent2. Spawn Tasks (each gets worktree path in prompt)3. Wait for all Tasks4. Sequential merge (abort on conflict → fall back to sequential)5. SINGLE deploy (coordinator only): git push && gh workflow run && gh run watch6. Cleanup worktrees```**SUBAGENT RULES (enforced by state file):**- If `coordinator: false`, NEVER run `gh workflow run` or `git push`- Commit locally in worktree only- Mark `needs_deploy: true` in checkpoint**Coordination detection:**- Skills set `coordinator: false`, `parallel_mode: true` in worktree `autonomous-state.json`- `deploy-enforcer.py` blocks subagent deploy attempts## Garbage Collection```bashpython3 ~/.claude/hooks/worktree-manager.py gc # Default 8-hour TTLpython3 ~/.claude/hooks/worktree-manager.py gc --dry-run # Preview cleanup```

Frequently asked questions

1716 Worktree Guide 43d9a9da