Clean Gone Branches

What it does

This skill detects local Git branches whose remote tracking branch has been removed and provides a safe, confirm-before-delete workflow to remove them. It integrates a small helper script that runs git fetch --prune, parses git branch -vv for : gone] markers, and then (after user confirmation) removes associated worktrees and deletes the local branches.

When to use it

Use this skill when cleaning a developer workstation or CI environment plagued by stale local branches — for example after large repo refactors, branch deletions, or long-lived feature branches that were removed on remote. Trigger it with phrases like “clean up branches”, “delete gone branches”, or “prune local branches”.

What's included

• Scripts: includes scripts/clean-gone which runs git fetch --prune and identifies gone branches (has_scripts=true).
• References: none listed.
• Instructions: the SKILL.md describes a three-step workflow: discover gone branches, present them and ask for a single yes/no confirmation, then remove any associated worktrees and delete the branches while reporting progress. The skill specifies the blocking question tool usage patterns across agent harnesses.

Compatible agents

This repo targets multi-harness developer assistants (Claude Code, Codex, Cursor, Gemini CLI). The instructions reference platform blocking tools (AskUserQuestion, request_user_input, ask_user), so it's suited to agents that can prompt for and receive interactive confirmations.