About worktree
A skill for managing Git worktrees as isolated agent sessions, with create, delete, and list operations. It requires human approval before disk mutations and enforces path and clean-tree safeguards.
Key features
- 01Creates, deletes, and lists worktrees
- 02Keeps worktree files under a dedicated path
- 03Checks for branch and directory collisions
- 04Blocks deletion of dirty worktrees
- 05Requires approval before mutations
Use cases
- 01Isolating repository work by branch
- 02Reviewing active worktrees and branches
- 03Preventing accidental removal of uncommitted work
Install
Copy the command and run it in a terminal.
$
npx skills add https:/ / github.com/ venhdev/ skills --skill worktreeAfter installing, type/worktreein Claude Code to confirm it loaded.
Details
From the project READMEworktree — Isolated Session & Branching Engine
Operating Invariants
- Path Isolation: Confine all branch edits, shell commands, and test executions strictly within
.agents/worktree/<branch>; forbid modifying root repository files from a worktree session. - Dirty Tree Breaker: Verify working tree cleanliness via
git status --porcelainbefore deleting a worktree; forbid deleting worktrees containing uncommitted modifications. - Pre-Mutation Gate: Stage worktree creation or removal in Canonical Changeset format and halt turn immediately; forbid executing worktree mutations on disk without affirmative human authorization.
Domain Rubric
1. Naming & Storage Conventions
<branch>: Strictly format as<type>/<slug>(feat/,fix/,refactor/,chore/,test/).<path>: Dedicated path strictly under.agents/worktree/<branch>.- Privacy Anchor: Root
.gitignoremust contain.agents/worktree/.
2. Supported Worktree Operations
[CREATE]: Add a new worktree branch checked out at target path.[DELETE]: Remove worktree directory and prune git administrative metadata.[LIST]: Inspect active worktrees and associated branches.
Canonical Output Contract
# Changeset: Git Worktree <Action>
`-- .agents/worktree/<branch>/
`-- [<ACTION>] <Worktree operation summary>.
Summary: 1 worktree affected (<branch>).
Execution Protocol
Phase 1: Pre-flight & Collision Audit
- For create: Inspect
git worktree listand verify no branch or directory collision exists. - For delete: Inspect
git status --porcelaininside target<path>. If dirty, halt immediately and report uncommitted files. - For list: Run
git worktree listand present active worktrees, halting turn immediately.
Phase 2: Staging & Authorization Gate
- Stage the planned worktree modification in Canonical Changeset format.
- Present the staging summary and halt turn immediately. Never execute git mutations without affirmative authorization.
Phase 3: Atomic Execution & Handoff
- On approval, execute the required operation:
- Create:
git worktree add <path> -b <branch> <base_ref> - Delete:
git worktree remove <path> && git worktree prune
- Create:
- Report operation completed with the absolute workspace path for IDE navigation.
Comments
Markdown supported