worktree-cleaner

Topics in the source

• Worktree Cleaner
• Hard rules
• Step 1: Inventory (read-only)
• Step 2: Present and ask
• Step 3: Remove one worktree
• Step 4: Ask about the branch
• Step 5: Final report
• Notes

Agents and parallel workflows create one git worktree per task, and nobody removes them. This skill finds them, shows the user what each one holds, and removes only what the user approves, checking the result after every step. The user decides. You gather evidence, recommend, and execute exactly what was approved. Nothing is removed in bulk without the user seeing the list first. 1. Ask before every destructive command. git worktree remove, git worktree prune, git worktree unlock and git branch -d/-D each need the user's approval for that worktree or that named group. Approval of one group does not carry to the next. 2. Never --force on work that would be lost. If a worktree has uncommitted changes, untracked files, or commits that exist nowhere else, show the exact files and commits and ask a separate, explicit question ("remove it and lose these changes?"). A general "yes, clean everything" is not that confirmation. 3. Never touch the main worktree, the worktree you are running in, or a worktree with live processes inside it (another Claude Code session, an editor, a dev server). Report them and move on. 4. Never delete a remote branch (git push --delete, git push origin :branch,

This is an excerpt. Refer to the complete source and its current requirements.