branch-cleanup

branch-cleanup is a skill for Claude Code, Codex from gspencergoog/skills. It costs 54 tokens per session (410 once invoked), scanned A, original, Apache-2.0.

A cleanup tool for local and remote Git branches that have already been merged into the main branch.

In plain words
What is it for?
It helps preview and delete merged branches, associated worktrees, and matching remote-tracking branches.
Why use it?
It removes stale branch references while checking normal merges, squash merges, linked worktrees, and uncommitted changes for safety.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit It helps preview and delete merged branches, associated worktrees, and matching remote-tracking branches.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/gspencergoog/skills/branch-cleanup
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add gspencergoog/skills --skill branch-cleanup
Clone the repo
git clone --depth 1 https://github.com/gspencergoog/skills

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for branch-cleanup

README.md
[![agentmods](https://agentmods.dev/badge/skills/gspencergoog/skills/branch-cleanup/github.svg)](https://agentmods.dev/skills/gspencergoog/skills/branch-cleanup)
Your own site
<a href="https://agentmods.dev/skills/gspencergoog/skills/branch-cleanup"><img src="https://agentmods.dev/badge/skills/gspencergoog/skills/branch-cleanup/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for branch-cleanup

Your own site · 80×15
<a href="https://agentmods.dev/skills/gspencergoog/skills/branch-cleanup"><img src="https://agentmods.dev/badge/skills/gspencergoog/skills/branch-cleanup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 54 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 410 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00054 $0.00410
Opus 5 $0.00027 $0.00205
Sonnet 5 $0.00011 $0.00082
Haiku 4.5 $0.00005 $0.00041

Measured 2d ago against content hash 553043df16dc, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

branch-cleanup scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/cleanup_branches.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/branch-cleanup/SKILL.md · 37 lines

What it actually says

Git Branch Cleanup Skill

This skill provides a helper script to identify and delete merged git branches. It handles both standard merges and squash merges (using git cherry analysis), and safely deletes matching tracking branches from their respective remotes (e.g. origin).

Core Features

  1. Squash-Merge Detection: Uses git cherry to check if a branch's changes exist in the main branch, even if the commit history was squashed.
  2. Worktree Cleanup: Automatically detects and deletes linked git worktrees associated with merged branches before deleting the branches.
  3. Safety First: Prevents removing the main worktree, and protects uncommitted work by aborting if a linked worktree has uncommitted changes.
  4. Remote Deletion: Automatically identifies and deletes the corresponding remote tracking branch (e.g. origin/my-branch) using branch tracking config, avoiding coincidental name matches.
  5. Dry-Run by Default: Safe exploration of branches before executing any deletion commands.

Usage

Run the bundled script in dry-run mode to preview changes:

python3 scripts/cleanup_branches.py --repo-dir /path/to/repo

To execute the deletions:

python3 scripts/cleanup_branches.py --repo-dir /path/to/repo --delete

Options:

  • --repo-dir <path>: Path to the target git repository (defaults to the current working directory).
  • --main-branch <name>: Name of the main/production branch to check against (defaults to main).
  • --delete: Executes the deletion of both local and tracking remote branches.
Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago Changed · +2 lines 553043df16dc
  2. 11d ago First seen · 35 lines · 54 tokens per session scan A 01a9e9e93415

Subscribe to this mod's changes

branch-cleanup is a skill published in the GitHub repository gspencergoog/skills (2 stars, last pushed today), licensed Apache-2.0. It adds 54 tokens to every session and 410 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

prowler-commit

Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.

prowler-cloud/prowler · 33 tokens

gh-auth-isolation

Safely manage multiple GitHub identities (EMU + personal) in agent workflows.

github/gh-aw · 20 tokens

comet-github

A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.

rpamis/comet · 72 tokens

github-skill

Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.

zeenie-ai/OpenCompany · 51 tokens

changelog-composer

Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".

Mathews-Tom/armory · 67 tokens

re0-merge

Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…

LilMGenius/paperthin · 70 tokens