---
name: Worktree Isolation
slug: worktree-isolation
category: DevOps
description: Worktree Isolation helps split implementation work into separate git worktrees so peers do not edit the same files at once. Use it when coordinating parallel changes, rerouting risky work, or avoiding overlap in a dirty main worktree.
github: "https://github.com/prassanna-ravishankar/repowire/tree/main/daemon-go/cli/assets/orchestrator/.agents/skills/worktree-isolation"
language: Go
stars: 260
forks: 34
install: "npx degit https://github.com/prassanna-ravishankar/repowire/tree/main/daemon-go/cli/assets/orchestrator/.agents/skills/worktree-isolation ~/.claude/skills/worktree-isolation"
installs_to: ~/.claude/skills/worktree-isolation
source_path: daemon-go/cli/assets/orchestrator/.agents/skills/worktree-isolation/SKILL.md
collection_size: 17
category_size: 828
collection_url: "https://dirskills.com/collections/prassanna-ravishankar/repowire"
added: 2026-09-02T05:20:20.048Z
last_synced: 2026-09-02T05:20:20.048Z
canonical_url: "https://dirskills.com/skills/worktree-isolation"
---

# Worktree Isolation

Worktree Isolation helps split implementation work into separate git worktrees so peers do not edit the same files at once. Use it when coordinating parallel changes, rerouting risky work, or avoiding overlap in a dirty main worktree.

**Install:**

```bash
npx degit https://github.com/prassanna-ravishankar/repowire/tree/main/daemon-go/cli/assets/orchestrator/.agents/skills/worktree-isolation ~/.claude/skills/worktree-isolation
```

## README

# Worktree Isolation

Use one worktree per independent implementation concern. This keeps peers from editing the same files blindly and makes review/cleanup tractable.

## When to isolate

Create or select an isolated worktree when:

- Two peers may implement in parallel.
- The change is large enough to outlive the current session.
- The work is speculative, risky, or likely to need review.
- The main worktree has unrelated dirty state.

Use the current worktree for small, direct, low-risk edits when it is clean enough and no other peer owns the same files.

## Before dispatch

Check:

```bash
git status --short --branch
git worktree list
repowire peer list
```

Tell the peer which worktree and branch it owns, what files are likely in scope, and whether it may commit or only report.

## Guardrails

- Do not put two implementation peers on overlapping files in the same worktree.
- Make one lane review-only when overlap is unavoidable.
- Stop or reroute stale peers before reassigning their write scope.
- Never clean up a worktree before checking dirty and unpushed work.