worktree
/worktree
Isolate a code-editing subagent when its change gets its own PR, the user asks for a worktree, or a skill opts in. NOT for serial edits or read-only agents.
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.
Unlicense, otwarta.
What it does and when to use it
Isolate a code-editing subagent when its change gets its own PR, the user asks for a worktree, or a skill opts in. NOT for serial edits or read-only agents.
Original author description
Isolate a code-editing subagent when its change gets its own PR, the user asks for a worktree, or a skill opts in. NOT for serial edits or read-only agents.
How it works
- Reconciling a worktree sub's commits into main
- Trust the diff, not the report
- Creating a worktree by hand
- Removing a worktree
SKILL.md preview
--- name: worktree description: Isolate a code-editing subagent when its change gets its own PR, the user asks for a worktree, or a skill opts in. NOT for serial edits or read-only agents. when_to_use: "change gets its own PR, user requests a worktree, reconcile worktree commits, remove a worktree, stale or prunable worktree, worktree registered under a missing path" --- # Worktree selection Use a worktree only when a subagent's change will get its own PR, the user explicitly requests one, or an applicable skill explicitly opts in. Otherwise, use the shared tree with one writer at a time. - NEVER use `isolation: "worktree"` — it creates a local branch; ALWAYS create a detached worktree by hand and brief the sub with its absolute path. - NEVER isolate a change only because a subagent writes it or it spans multiple files — ALWAYS use the delivery boundary, the user's request or an applicable skill's explicit opt-in. - NEVER run concurrent writers on the shared tree — ALWAYS include the parent agent, code-editing subagents and write-producing tools in the one-writer rule. - NEVER worktree-isolate a READ-ONLY sub (review / verify / research) — ALWAYS let those share a stable tree. - NEVER treat a worktree as full isolation — ALWAYS coordinate shared services, ports, caches and external resources. ## Reconciling a worktree sub's commits into main - NEVER `git cherry-pick` a worktree sub's commits — on linked worktrees it silently empties the commit and slips HEAD. - ALWAYS record the fork SHA when the worktree is created and apply the sub's diff against it, scoped to the sub's own files so out-of-scope edits don't leak in: ```bash git diff <fork-base> <sub-tip> -- <sub-owned-files> | git apply --3way ``` - NEVER proceed past a `git apply --3way` that reports conflicts — ALWAYS stop, resolve the rejects by hand, then continue. ## Trust the diff, not the report - NEVER act on a sub's "done / green / committed" claim — ALWAYS read its diff (`git diff --name-only <fork-base> <sub-tip>`) and confirm the claimed change is actually there. ## Creating a worktree by hand ALWAYS resolve the base to a commit SHA, then create the sub's checkout: ```bash git worktree add --detach <repo-root>/.<name> <sha> ``` A hidden dir in the repo root, NEVER a sibling; a bare `worktree add` attaches a branch, so ALWAYS `--detach`. ALWAYS give the sub that path, the fork SHA and its owned files; require all edits there and verify `git -C <path> branch --show-current` prints nothing. ALWAYS reconcile and verify the diff before removing it (§ Removing a worktree). ## Removing a worktree Removal deletes the directory, files included: the one lift of WISDOM § Shell's ban on recursive removal, and it covers `git worktree remove --force` only. ALWAYS remove this task's worktree once reconciled, and a worktree the user asks removed; NEVER another task's worktree on your own call. ALWAYS pass both checks first, in this order, and state each result: 1. Its HEAD is kept: `git branch -a --contains <sha>` (sha from `git worktree list`) prints a ref, or its diff is reconciled into main. Else ALWAYS save it first: `git update-ref refs/keep/<name> <sha>`. 2. Its uncommitted changes are shown — `git -C <path> status --porcelain` and `git -C <path> diff` — and either called throwaway in the reply or saved first: `git -C <path> stash push -u -m <name>` (the stash lives in the shared repo; `git stash list` from the main tree shows it). Then: ```bash git worktree remove --force <path> && git worktree prune ``` - When `git -C <path>` fails with "not a git repository" because the worktree was registered under a path this machine lacks (a host path, seen from a container), ALWAYS run `git worktree repair <path>` from the main tree first; it rewrites both pointers, and the checks and the removal then run as above. NEVER `git worktree prune` before the checks: it drops the admin dir the diff needs. - When a mount point inside the directory survives `remove --force`, ALWAYS finish by hand: delete the files `find <path> -xdev -type f` lists, `rmdir` the emptied dirs, then `git worktree prune`; the mount points stay — name them in the reply. NEVER `rm -r` for this: the Shell ban holds, and the permission deny list refuses it.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · kronael/tools | 100 | Unlicense |
| vanducng/skills | 100 | MIT |
| tony/skills | 100 | MIT |
| zts212653/clowder-ai | 100 | MIT |
| duronext/jig | 100 | MIT |
| guangshinhaha/shinstack | 100 | MIT |
| PranamRDoshi/dotclaude | 100 | MIT |
| rhesis-ai/rhesis | 100 | MIT |
| zipstack/unstract | 100 | AGPL-3.0 |
Database snapshot: 13.11.2026 · package version 1837b7122761 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100worktree-per-agent
Isolate an agent's work in its own git worktree branched off the default branch, so two agents never land conflicting changes on the shared checkout. Use at the start of any implementation task in a repo where others may also be working, and whenever a repo's instructions say "work in a worktree". - 100git-worktree
Use when the user asks to work in a worktree or to isolate the agent's work from other agents in the same checkout. - 100fork-worktree
Use when user wants to create new autonomy branch with dedicated worktree for parallel agent workflows - 100worktree-new
Create a task worktree with `aidrian worktree new` and run the project's bootstrap. Use when a task needs one. - 100isolate-branch
[Orbit 2.4.5 Implementation] An isolated branch or worktree for the task, within scope. Use when: «отдельная ветка», «worktree», «изолируй задачу», «не трогай текущую ветку»; new branch, worktree, isolate work. - 86coordinate
Run several coding agents on one repository as a coordinator, each worker in its own git worktree with a plan-first session prompt. Use when the user wants to plan sessions, launch and watch workers, review plans, check CI and merge their PRs one at a time. Opt-in.