ce-clean-gone-branches

To clean up local git branches with gone remotes, run a fetch with prune to detect stale tracking references, then delete the branches and any associated worktrees. The workflow lists affected branches and asks for confirmation before removal.

When deleting a stale local branch, associated git worktrees are also removed. The cleanup workflow identifies branches marked as gone on the remote and safely removes both the branch and any linked worktree directories during the deletion process.

Git fetch prune removes remote tracking references that no longer exist on the remote repository. After pruning, local branches that previously tracked those deleted remotes are marked as gone, which can be detected using git branch -vv for cleanup.

Deleting stale local branches is safe because the workflow preserves your current branch and provides a guided confirmation flow. It presents affected branches for review before removing them and any associated worktrees, ensuring you approve the changes.

Local branches remain after a remote is deleted because git does not automatically remove local tracking branches. You need to run a fetch with prune to update remote tracking references, then detect and delete the gone branches manually or via a cleanup workflow.