What problem does it solve?
Git worktrees spawned by agent harnesses (warp, codex, opencode, conductor) accumulate with nothing reaping them, and deleting them blindly destroys uncommitted work. This Skill provides a safe, auditable procedure for deciding which worktrees and branches can be removed and which must be preserved.
Core Features & Use Cases
- Containment-based audit: Classifies every worktree using
git merge-base --is-ancestor against origin/main and git cherry to count unmerged commits, rather than trusting self-reported merge status.
- Decision matrix for reaping: Distinguishes merged-and-clean worktrees, throwaway dirt (lockfile churn), real uncommitted work, detached-HEAD states, and stacked branches, with exact commands for each case.
- Repo-specific safeguards: Covers shared-stash hazards, animal-named stacked warp branches, HEAD verification before committing, and the one-owner-per-worktree invariant.
- Use Case: After several agent sessions, run a periodic sweep: audit all worktrees, present an approve-list of exact removal commands grouped by tier, reap the safe ones, anchor detached work into
holding/* branches, and finish with git worktree prune.
Quick Start
Audit all Git worktrees in this repository and tell me which ones are safe to remove, then reap the approved ones.
