git-clean-gone-branches

To clean gone git branches, run git fetch --prune to discover stale remote tracking references, list the local branches for review, and safely remove them after a confirmation prompt. Associated worktrees are removed before branch deletion to ensure a clean state.

The safest way to delete stale git worktrees and branches is to use a confirmation step that prevents accidental data loss, removing any associated worktrees first before deleting the local branches to maintain repository integrity.

Git fetch --prune performs discovery by syncing remote tracking references, allowing the cleanup process to accurately identify and list local git branches whose remote counterparts have been deleted and are ready for safe removal.

Yes, you can automate stale branch cleanup across multiple workspaces by running this skill in automation scripts, which handles discovering gone branches and removing them along with their associated worktrees safely.

A confirmation step is needed when removing gone git branches to prevent accidental data loss in shared repositories, ensuring you review the list of stale local branches before approving their deletion.

Stale branch cleanup works for onboarding workflows by removing local git branches whose remote tracking branches have been deleted, reducing repository clutter when new workspaces accumulate stale branches.