cleanup-local-branches SKILL.md skillA
cleanup-local-branches from pekral/cursor-rules is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add pekral/cursor-rules/cleanup-local-branches@git:20260613.ac1fa4ePins git:20260613.ac1fa4e in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- pekral/cursor-rules
- Path
skills/cleanup-local-branches/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260613.0432f6a, committed Jun 13, 2026
- First version recorded
- Jun 13, 2026
- Size
- 8,910 bytes
- Repository stars
- 12
- License
- MIT
Use when cleaning up local Git branches after origin pruning. Deletes local branches whose upstream was deleted on origin (marked gone) and local branches with no origin counterpart that have been inactive for more than six months, while always protecting the current branch and the default branches. Previews every deletion before running it.
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
# Cleanup Local Branches ## Purpose Prune dead local branches so the working copy only keeps branches that are still alive on origin or still recently active. Two deletion categories: - **Gone** — local branches whose upstream tracking branch was deleted on origin (e.g. the PR was merged and the origin branch removed). - **Stale** — local branches that have **no** counterpart on origin and have not received a commit for **more than six months**. --- ## Constraints - Apply `@rules/git/general.mdc` - Output must be in English - This skill deletes **local** refs only — it never deletes, force-pushes, or modifies any branch on origin - Never delete the currently checked-out branch - Never delete protected branches: `main`, `master`, `develop`, `development`, `production`, `staging`, or any branch matching `release/*` or `hotfix/*` - Always print the full deletion preview (branch, category, last commit date, merge status, planned action) **before** deleting anything - Never rewrite history, force-push, or run `git gc` / `git reflog expire` - Do not delete an unmerged branch automatically — keep it and report it unless the user explicitly authorizes force deletion --- ## Use when …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_f2egnu3gtunmpjn5/dd4256a27fb7065f9655fea959283ef6af55db9c01952bb9a4cf1abc5b8142b9.json
Then /plugin install cleanup-local-branches@markdownregistry-f2egnu3gtunmpjn5 in Claude Code. It installs git:20260613.0432f6a, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add pekral/cursor-rules/cleanup-local-branches@sha256:2a111ebfe27ae61bThe line at the top of this page pins the label git:20260613.ac1fa4e, 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_f2egnu3gtunmpjn5)
2 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in pekral/cursor-rules/cleanup-local-branches since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of cleanup-local-branches from somewhere else? Ask it: where did my cleanup-local-branches come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 2 versions of this file, all committed on Jun 13, 2026.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260613.0432f6a latest | 2026-06-13 | 0432f6a | 8,910 B | A | view · diff |
| git:20260613.ac1fa4e | 2026-06-13 | ac1fa4e | 6,057 B | A | view |
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/cleanup-local-branches/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
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 (8910 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
pekral/cursor-rules · 12 stars · license MIT · pushed 2026-10-03 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_f2egnu3gtunmpjn5 GET https://markdownregistry.com/api/v1/resolve?ref=pekral/cursor-rules/cleanup-local-branches GET https://markdownregistry.com/api/v1/blob/2a111ebfe27ae61be417ffa63a4275c8581e387b9e28e9e4876dae6edac3c8e4
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.