# Assess Worktree Isolation

> Assesses checkout isolation when concurrent edits or dirty files may collide with a new task; reuses safe worktrees and preserves unrelated work rather than creating or deleting blindly.

- Skill: `jovanipink/assess-worktree-isolation` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx get-skill add jovanipink/assess-worktree-isolation`
- Raw SKILL.md: https://api.skillmd.com/api/skills/jovanipink/assess-worktree-isolation/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- License: MIT
- Author: JovaniPink (https://skillmd.com/u/jovanipink)
- Updated: 2026-11-15
- Page: https://skillmd.com/skills/jovanipink/assess-worktree-isolation

---


# Worktree Isolation

Protect concurrent and unrelated repository work by assessing isolation before mutation.

Read [linked worktree model](references/linked-worktree-model.md) when the decision depends on shared repository state, submodules, pruning, locking, or repair.

## Workflow

1. Inspect the current branch, revision, status, existing worktrees, and target files without changing them.
2. Identify ownership overlap, uncommitted work, branch conflicts, shared generated output, and commands that can affect all worktrees.
3. Decide whether the work can proceed in place, needs a linked worktree, or must wait for coordination.
4. Propose the exact branch, base revision, worktree path, ownership boundaries, validation, and cleanup conditions.
5. Require explicit authority before creating, moving, locking, repairing, pruning, or removing a worktree.
6. Recheck the shared repository state before cleanup. Preserve worktrees with uncommitted or unintegrated work.

## Done when

The assessment is done when the isolation decision and proposed layout are stated with the authority each step needs. Stop and ask before any worktree change that is not already authorized.

## Boundaries

- Linked worktrees share repository-level state, including refs and some configuration; they are not independent clones.
- Do not assign the same branch to multiple worktrees.
- Treat submodule-heavy repositories cautiously because linked-worktree support can be incomplete.
- Never remove a worktree or branch merely because another change is complete.

## Output

Lead with the answer. Use the shortest format that retains the required evidence and limits; expand when requested or needed. The items below describe required content, not mandatory headings.

Report `Current state`, `Collision risks`, `Isolation decision`, `Proposed layout`, `Required authority`, `Validation`, and `Cleanup conditions`.

## Example

Synthetic example; not an observed client result.

Input: A checkout contains an unrelated uncommitted patch.

Output: Preserve the patch and inspect available worktrees. Isolate the new task only if a safe existing checkout cannot serve it.

