git-post-merge-cleanup SKILL.md skillA
git-post-merge-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-post-merge-cleanup@v1.3.0Pins v1.3.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/git/git-post-merge-cleanup/SKILL.md- Versions recorded
- 5
- Latest version
- v1.3.0, committed Oct 8, 2026
- First version recorded
- May 20, 2026
- Size
- 9,385 bytes
- Repository stars
- 11
- License
- MIT
Clean up everything stale after merges in one pass: local branches fully merged into the default branch, remote-tracking refs whose remote is gone, and worktrees that look "modified" but are already on main. Scans, classifies, presents a clear plan, and only acts on confirmation. Supports `--dry-run` and `--yes`. Use whenever the user mentions cleaning up branches OR worktrees, tidying git state after a batch of PRs landed, or noticing stale debris. Trigger on: "clean up 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 Post-Merge Cleanup After a batch of PRs land, the local repo accumulates debris: fully merged branches, tracking refs whose remote was deleted by GitHub, and worktrees that still show "modified" files even though those changes are already on main. This skill cleans all of it in one pass — scan, classify, present a plan, confirm, execute. The scan is cheap; always do both classes. ## Flags - `--dry-run` — scan and present the plan, but do not delete anything. - `--yes` — skip the confirmation prompt. Still presents the plan first. Default (no flags): scan, present plan, wait for confirmation. ## Step 1 — Refresh remote state The default scan and `--dry-run` are read-only: use existing refs and `git ls-remote --heads --tags origin` to observe remote state without updating local refs. Record freshness; remote failure means UNKNOWN, not safe to delete. Fetch/prune is an optional approved mutation, never part of the nonmutating preview. Tags: scan and classify tags nonmutantly before any deletion actions. …
Read the whole file at its exact version.
How to install
mdr add ivy00johns/skill-madness/git-post-merge-cleanup@sha256:adf8f6a669e1ea0aThe line at the top of this page pins the label v1.3.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_jis4q7vlitzaazee)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between May 20, 2026 and Oct 8, 2026, about one every 35 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.3.0 latest | 2026-10-08 | d1d8537 | 9,385 B | A | view · diff |
| v1.2.0 | 2026-09-24 | 2b13542 | 8,065 B | A | view · diff |
| v1.1.1 | 2026-07-04 | 93d1c20 | 7,085 B | A | view · diff |
| v1.1.0 | 2026-05-20 | bc9aa5a | 7,084 B | A | view · diff |
| v1.0.0 | 2026-05-20 | 63b19b5 | 7,200 B | A | view |
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 (9385 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_jis4q7vlitzaazee GET https://markdownregistry.com/api/v1/resolve?ref=ivy00johns/skill-madness/git-post-merge-cleanup GET https://markdownregistry.com/api/v1/blob/adf8f6a669e1ea0a70bd8f3e5e85df6b21c1a974c31edc9a72551d40e3991cc7
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.
More from ivy00johns/skill-madness
Every file in ivy00johns/skill-madness