git-clean-gone-branches
Clean up local branches whose remote tracking branch is gone. Use when the user says "clean up branches", "delete gone branches", "prune local branches", "clean gone", or wants to remove stale local branches that no longer exist on the remote. Also handles removing associated worktrees for branches that have them.
Best use case
git-clean-gone-branches is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Clean up local branches whose remote tracking branch is gone. Use when the user says "clean up branches", "delete gone branches", "prune local branches", "clean gone", or wants to remove stale local branches that no longer exist on the remote. Also handles removing associated worktrees for branches that have them.
Teams using git-clean-gone-branches should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/git-clean-gone-branches/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How git-clean-gone-branches Compares
| Feature / Agent | git-clean-gone-branches | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Clean up local branches whose remote tracking branch is gone. Use when the user says "clean up branches", "delete gone branches", "prune local branches", "clean gone", or wants to remove stale local branches that no longer exist on the remote. Also handles removing associated worktrees for branches that have them.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
AI Agents for Coding
Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.
AI Agents for Marketing
Discover AI agents for marketing workflows, from SEO and content production to campaign research, outreach, and analytics.
AI Agents for Startups
Explore AI agent skills for startup validation, product research, growth experiments, documentation, and fast execution with small teams.
SKILL.md Source
# 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 bash scripts/clean-gone ``` [scripts/clean-gone](./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 question tool (e.g., `AskUserQuestion` in Claude Code, `request_user_input` in Codex, `ask_user` in Gemini). If no question tool is available, present the list and wait for the user's reply before proceeding. 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: 1. Check if it has an associated worktree (`git worktree list | grep "\\[$branch\\]"`) 2. If a worktree exists and is not the main repo root, remove it first: `git worktree remove --force "$worktree_path"` 3. 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.
Related Skills
skill-one
Sample skill
disabled-skill
A skill with model invocation disabled
default-skill
No description provided.
custom-skill
No description provided.
todo-triage
Use when reviewing pending todos for approval, prioritizing code review findings, or interactively categorizing work items
todo-resolve
Use when batch-resolving approved todos, especially after code review or triage sessions
todo-create
Use when creating durable work items, managing todo lifecycle, or tracking findings across sessions in the file-based todo system
test-xcode
Build and test iOS apps on simulator using XcodeBuildMCP. Use after making iOS code changes, before creating a PR, or when verifying app behavior and checking for crashes on simulator.
test-browser
Run browser tests on pages affected by current PR or branch
slfg
Full autonomous engineering workflow using swarm mode for parallel execution
setup
Configure project-level settings for compound-engineering workflows. Currently a placeholder — review agent selection is handled automatically by ce:review.
resolve-pr-feedback
Resolve PR review feedback by evaluating validity and fixing issues in parallel. Use when addressing PR review comments, resolving review threads, or fixing code review feedback.