git-branch-cleanup SKILL.md skillA
git-branch-cleanup from ivy00johns/skill-madness is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add ivy00johns/skill-madness/git-branch-cleanup@v1.2.0Pins v1.2.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- ivy00johns/skill-madness
- Path
skills/archive/git-branch-cleanup/SKILL.md- Versions recorded
- 1
- Latest version
- v1.2.0, committed May 17, 2026
- Size
- 5,666 bytes
- Repository stars
- 11
- License
- MIT
Clean up stale and merged git branches — both local and remote. Prunes tracking refs, identifies merged branches safe to delete, flags orphaned branches whose remote is gone, and presents a clear summary before acting. Use this skill whenever the user mentions cleaning up branches, pruning stale branches, deleting old branches, or tidying their git state. Trigger on: "clean up branches", "delete merged branches", "prune branches", "stale branches", "branch cleanup", "tidy branches…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Git Branch Cleanup Systematically identify and remove branches that are no longer needed. Stale branches accumulate fast — especially when PRs auto-delete the remote branch on merge but the local tracking ref and local branch stick around. This skill walks through the cleanup safely so nothing important gets lost. ## Workflow ### Step 1: Refresh remote state Start by fetching and pruning so the local view of remote branches is accurate. Without this, you'd see stale `origin/*` refs for branches GitHub already deleted on merge. ```bash git fetch origin --prune ``` ### Step 2: Detect the default branch Don't assume `main` — check: ```bash git symbolic-ref -q --short refs/remotes/origin/HEAD 2>/dev/null | sed 's@^origin/@@' ``` The `-q` flag suppresses the fatal error when `origin/HEAD` isn't set, and `--short` strips the `refs/remotes/` prefix. If that fails, fall back to checking whether `main` or `master` exists locally. Use the result as `$DEFAULT` for the rest of the workflow. ### Step 3: Categorize every branch Run these four commands and cross-reference the results: | Command | Purpose | |---|---| …
Read the whole file at its exact version.
How to install
mdr add ivy00johns/skill-madness/git-branch-cleanup@sha256:a18174b42e8614d0The line at the top of this page pins the label v1.2.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_2fx6evnpkmpoa7qy)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on May 17, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (5666 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
ivy00johns/skill-madness · 11 stars · license MIT · pushed 2026-10-25 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_2fx6evnpkmpoa7qy GET https://markdownregistry.com/api/v1/resolve?ref=ivy00johns/skill-madness/git-branch-cleanup GET https://markdownregistry.com/api/v1/blob/a18174b42e8614d033e76cd4233e9e4fd332070a56722753f7c32b4687a59ae1
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.