safe-bulk-worktree-branch-cleanup SKILL.md skillA
safe-bulk-worktree-branch-cleanup from wan-huiyan/agent-traffic-control is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add wan-huiyan/agent-traffic-control/safe-bulk-worktree-branch-cleanup@v1.1.0Pins v1.1.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- wan-huiyan/agent-traffic-control
- Path
plugins/agent-traffic-control/skills/safe-bulk-worktree-branch-cleanup/SKILL.md- Versions recorded
- 5
- Latest version
- v1.1.0, committed Sep 17, 2026
- First version recorded
- May 29, 2026
- Size
- 9,482 bytes
- Repository stars
- 3
- License
- MIT
Bulk delete accumulated git worktrees and branches without losing anything — "this repo is messy with worktrees", "too many branches", "tidy it up but keep X". Use when `git worktree list` or `git branch -a` prints dozens of stale entries. The trap: `git branch --merged` and `git merge-base --is-ancestor` report a squash merged branch as NOT merged, so they call almost everything unmerged and you stop, or delete believing you are losing work. Gate on the pull request's state instead. Salvages…
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
# Safe Bulk Worktree & Branch Cleanup ## Problem A repo accumulates dozens of git worktrees and branches over many sessions. The user wants them cleaned up "without losing progress." Bulk-deleting is risky in two non-obvious ways: 1. **Ancestry tests lie about squash-merged branches.** `git branch --merged` and `git merge-base --is-ancestor` only detect merge-commit / fast-forward merges. A squash merge creates a *new* commit on the trunk — the original branch tip is never an ancestor. In a squash-merge repo (PR titles ending `(#NN)`), these tools flag *almost every* merged branch as "NOT merged." Trusting them either blocks the cleanup or, worse, makes you think real work would be lost. 2. **`git worktree remove` silently discards untracked files.** Removing a worktree never deletes commits (the branch + history persist), but any *uncommitted / untracked* files in that worktree's directory are gone. ## Context / Trigger Conditions - User: "this repo is messy with all the worktrees", "clean up the branches", "review the rest and help me clean up without losing progress". - `git worktree list` shows many `.claude/worktrees/*` or `/tmp/*` entries. …
Read the whole file at its exact version.
How to install
mdr add wan-huiyan/agent-traffic-control/safe-bulk-worktree-branch-cleanup@sha256:d3797014dc336716The line at the top of this page pins the label v1.1.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_qwdfsxmci3rpebth)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between May 29, 2026 and Sep 17, 2026, about one every 28 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.1.0 latest | 2026-09-17 | 5ad1266 | 9,482 B | A | view · diff |
| v1.0.0 | 2026-08-10 | 5b6d8a2 | 7,968 B | A | view · diff |
| v1.0.0 | 2026-08-10 | a58c34c | 7,949 B | A | view · diff |
| v1.0.0 | 2026-08-10 | a39e221 | 8,064 B | A | view · diff |
| v1.0.0 | 2026-05-29 | 059688a | 7,183 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 (9482 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
wan-huiyan/agent-traffic-control · 3 stars · license MIT · pushed 2026-09-22 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_qwdfsxmci3rpebth GET https://markdownregistry.com/api/v1/resolve?ref=wan-huiyan/agent-traffic-control/safe-bulk-worktree-branch-cleanup GET https://markdownregistry.com/api/v1/blob/d3797014dc336716eaf7d4316daea9c58e3c5e32f24159a72f71546aae169e95
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.