cleanup-git-worktrees

Run the audit command to classify every worktree and branch, review the grouped table of deletable versus protected targets, then run the clean command with explicit branch names and --apply. The script re-verifies each target before deleting and refuses anything not classified as a candidate.

Squash merges leave no ancestry, so git merge-base reports not merged. Use the gh CLI to check that the PR state is MERGED and the local tip equals the PR head SHA, or search the base branch log for each extra commit's subject.

No. Any branch with unpushed commits is classified as review-gone-unpushed or otherwise protected, and the clean command refuses to delete it. Zero unpushed commits means every local commit is reachable from a remote ref, so deletion loses nothing.

Dirty worktrees are classified as protect-dirty and are never deleted. Untracked paths matching the noise regex, such as node_modules, do not count as dirt and are removed together with the worktree using git worktree remove --force.

A prunable entry means the worktree registration points to a gitdir that no longer exists, usually after a partial removal. Running git worktree prune drops only the registration; any leftover directory must be inspected and removed manually after user approval.

Yes. Without the --apply flag, the clean command only prints what would be removed. Even with --apply, it re-classifies each target immediately before deletion and aborts on anything that is not a verified candidate.