Skill

git-clean-gone-branches

Deletes local Git branches whose remote tracking branches are gone, including associated worktrees, after user confirmation. Activates on 'clean up branches', 'delete gone branches', 'prune local branches', or similar.

Git

git-workflow

npx claudepluginhub sunrain520/spec-first

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Delete local branches whose remote tracking branch has been deleted, including any associated worktrees.

Supporting Assets

scripts/clean-gone

SKILL.md

Similar Skills

git-clean-gone-branches

13.2k

Deletes local Git branches with gone remote tracking after confirmation, including worktrees. Run discovery script, list branches, confirm y/n, then prune.

1 file

compound-engineering

clean-branches

129

Safely identifies and deletes merged and stale Git branches after fetching latest state, filtering by pattern, and user confirmation via interactive prompts. Protects main branches.

1 file3 tools

claude-coding

git-cleanup

4.2k

Safely analyzes and cleans up local git branches/worktrees: categorizes merged/squash-merged/superseded/active, groups related ones, deletes only after user approval.

4 tools

git-cleanup

Stats

Stars23

Forks4

Last CommitApr 25, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Clean Gone Branches

Delete local branches whose remote tracking branch has been deleted, including any associated worktrees.

Workflow

Step 1: Discover gone branches

Run the discovery script to fetch the latest remote state and identify gone branches:

bash scripts/clean-gone

The script runs git fetch --prune first, then parses git branch -vv for branches marked : gone].

If the script outputs __NONE__, report that no stale branches were found and stop.

Step 2: Present branches and ask for confirmation

Show the user the list of branches that will be deleted. Format as a simple list:

These local branches have been deleted from the remote: - feature/old-thing - bugfix/resolved-issue - experiment/abandoned Delete all of them? (y/n)

Wait for the user's answer using the platform's blocking question tool: AskUserQuestion in Claude Code (call ToolSearch with select:AskUserQuestion first if its schema isn't loaded) or request_user_input in Codex. Fall back to presenting the list in chat only when no blocking tool exists in the harness or the call errors (e.g., Codex edit modes) — not because a schema load is required. Never silently skip the question.

This is a yes-or-no decision on the entire list -- do not offer multi-selection or per-branch choices.

Step 3: Delete confirmed branches

If the user confirms, delete each branch. For each branch:

Check if it has an associated worktree (git worktree list | grep "\\[$branch\\]")

If a worktree exists and is not the main repo root, remove it first: git worktree remove --force "$worktree_path"

Delete the branch: git branch -D "$branch"

Report results as you go:

Removed worktree: .worktrees/feature/old-thing Deleted branch: feature/old-thing Deleted branch: bugfix/resolved-issue Deleted branch: experiment/abandoned Cleaned up 3 branches.

If the user declines, acknowledge and stop without deleting anything.