git-clean-gone-branches

To delete local Git branches whose remote has been deleted, this Skill runs git fetch --prune to refresh state and uses git branch -vv to identify gone entries, then removes them after user approval.

Yes, you can clean up stale local branches using Git worktrees. The Skill safely removes associated worktrees before deleting the branches to prevent orphaned references in your repository.

The best way to automatically prune gone branches is running a cleanup workflow that fetches the latest remote state, identifies stale branches marked as gone, and deletes them following a user confirmation step.

Yes, the branch cleanup process requires confirmation. The Skill presents the discovered list of stale branches to the user and only proceeds with deletions after receiving explicit approval.

Git fetch --prune leaves orphaned local branches behind because it only removes remote tracking references. You need a separate branch cleanup process to identify gone entries and delete the local branches.

To find which local branches have gone remote tracking entries, the Skill runs git branch -vv after refreshing the remote state, identifying branches marked as gone for targeted removal.