cleanup-git-worktrees

Run the audit command to classify every worktree and branch, review the table of candidates, then pass exact branch names to the clean command with --apply. The script re-audits each target immediately before deletion and refuses anything not merged or gone.

Use git merge-base --is-ancestor to test whether a branch is contained in the base ref, which the audit script does automatically. Branches fully contained in the base are classified as candidate-merged and become eligible for cleanup.

No, a [gone] upstream only means the remote branch was deleted, which often happens after squash merges or rebases without proving containment. The audit classifies these separately as candidate-gone and recommends checking GitHub PR state when the distinction matters.

No, any worktree with modified or untracked files is classified as protect-dirty and is never removed. The clean command also refuses to delete the current worktree, protected branches like main, or branches lacking merge or gone-upstream evidence.

Yes, the clean command runs as a dry run by default and prints each target branch, worktree path, and classification without deleting anything. Deletion only occurs when you explicitly pass the --apply flag.