How do I install the Git Clean Gone Branches skill?

Run npx skillmds@latest add sitaggart/git-clean-gone-branches in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Git Clean Gone Branches safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Git Clean Gone Branches?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Git Clean Gone Branches free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Git Clean Gone Branches?

SiTaggart (@sitaggart) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Git Clean Gone Branches by sitaggart

Name: Git Clean Gone Branches
Rating: 4.2 (5 reviews)
Author: SiTaggart

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.

SiTaggart Updated Sep 10, 2026

File contents

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

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 (fall back to a question in chat when the tool is unavailable). 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.

---name: git-clean-gone-branchesdescription: 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.---# Clean Gone BranchesDelete local branches whose remote tracking branch has been deleted, including any associated worktrees.## Workflow### Step 1: Discover gone branchesRun the discovery script to fetch the latest remote state and identify gone branches:```bashbash 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 confirmationShow 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/abandonedDelete all of them? (y/n)```Wait for the user's answer using the platform's blocking question tool (fall back to a question in chat when the tool is unavailable). 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 branchesIf 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-thingDeleted branch: feature/old-thingDeleted branch: bugfix/resolved-issueDeleted branch: experiment/abandonedCleaned up 3 branches.```If the user declines, acknowledge and stop without deleting anything.

Frequently asked questions