cleanup-dangling-worktrees

To automatically remove Git worktrees for merged branches, run a cleanup process that verifies Pull Request merge status via GitHub CLI and safely prunes associated worktrees while preserving active development branches and uncommitted changes.

A dangling Git worktree is a stale working directory left behind after a feature branch is merged. You should prune worktrees after completing development cycles to clear clutter and prevent confusion in your repository.

Yes, you need the GitHub CLI (gh) to clean up stale Git worktrees safely. The process requires gh to verify whether associated Pull Requests have been merged before removing the worktree directories.

Automatically deleting Git worktrees with uncommitted changes is prevented by strict safety checks. The cleanup process scans for uncommitted changes, unpushed commits, and open PRs to ensure active development worktrees are preserved.

The best way to clean up Git worktrees after merging a PR is to use an automated cleanup skill that identifies stale worktrees, verifies PR merge status using gh, and removes them while applying strict checks against deleting active branches.