Does this skill work with any Git hosting provider?

Yes, it works with any Git repository regardless of the host (GitHub, GitLab, Bitbucket) as long as the remote tracking info is correctly set.

What does a branch marked as [gone] mean?

A branch is marked as [gone] in Git when its upstream (remote) counterpart has been deleted, but the local branch still exists in your repository.

Is it safe to force-delete these branches?

Yes, because the [gone] status indicates the code has already been merged or the branch was intentionally removed from the remote source of truth.

Why are some branches skipped during cleanup?

The skill automatically skips branches that have associated Git worktrees to prevent accidental disruption of active development environments.

Git Gone Branch Cleaner

Name: Git Gone Branch Cleaner
Author: mixomat

bymixomat

Developer Tools

Automates the removal of local Git branches that have been deleted from remote repositories to maintain a clean workspace.

About

The clean-gone-branches skill helps developers maintain repository hygiene by identifying and removing local branches that no longer exist on the remote server (marked as '[gone]'). It intelligently scans your local branch list, identifies stale references, and performs a force-deletion to ensure your local environment stays synchronized with the remote. Crucially, it includes safety logic to skip branches with active Git worktrees, preventing accidental data loss and providing clear reporting on exactly what was cleaned or skipped.

Key Features

Automatic identification of stale branches marked as [gone]
Safety protection for branches with active Git worktrees
Detailed summary reports of deleted versus skipped branches
0 GitHub stars
Force-deletion of merged or deleted remote branches
Non-destructive scanning of current repository state

Use Cases

Cleaning up local branches after a major sprint or project milestone
Removing stale feature branches that have been merged and deleted on GitHub or GitLab
Synchronizing local environment after remote repository pruning

About

Key Features

Automatic identification of stale branches marked as [gone]
Safety protection for branches with active Git worktrees
Detailed summary reports of deleted versus skipped branches
0 GitHub stars
Force-deletion of merged or deleted remote branches
Non-destructive scanning of current repository state

Use Cases

Cleaning up local branches after a major sprint or project milestone
Removing stale feature branches that have been merged and deleted on GitHub or GitLab
Synchronizing local environment after remote repository pruning