git-clean-worktrees SKILL.md skillA
git-clean-worktrees 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-clean-worktrees@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
- ivy00johns/skill-madness
- Path
skills/archive/git-clean-worktrees/SKILL.md- Versions recorded
- 1
- Latest version
- v1.1.0, committed May 17, 2026
- Size
- 6,245 bytes
- Repository stars
- 11
- License
- MIT
Clean up stale git worktrees whose work is already on the main branch. Worktrees accumulate after branches are merged — they sit around with "modified" files that look like uncommitted work but are actually already on main. This causes confusion ("did I forget to merge this?") and clutters git status. Use this skill whenever the user mentions stale worktrees, worktree cleanup, leftover worktrees, "clean up workspaces", or when you notice orphaned worktrees during other git operations. Also…
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
# Clean Worktrees Systematically find and remove git worktrees whose work is already on the main branch. The core problem this solves: worktrees created during feature work persist after the branch is merged, showing "modified" files that are actually already committed — creating confusion about what's merged and what isn't. ## Why This Happens Worktrees are created for isolation during feature work. When the branch gets merged (squash-merge, regular merge, or cherry-pick), the worktree doesn't disappear. It still has the branch checked out, and `git status` inside it shows modifications relative to the worktree's HEAD — but those changes are already on main. The worktree is stale but looks active. ## Workflow ### Step 1: List all worktrees ```bash git worktree list ``` Identify the **main worktree** (the repo root) — it must never be removed. Everything else is a candidate for cleanup. If there's only the main worktree, report "No secondary worktrees found" and stop. ### Step 2: For each secondary worktree, determine if it's stale Run these checks in order. A worktree is **safe to remove** if ANY of these conditions is true: #### Check A: Branch is merged into main …
Read the whole file at its exact version.
How to install
mdr add ivy00johns/skill-madness/git-clean-worktrees@sha256:2a44fd4524f455f1The 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_erfl5l56mi5pq75p)
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 (6245 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_erfl5l56mi5pq75p GET https://markdownregistry.com/api/v1/resolve?ref=ivy00johns/skill-madness/git-clean-worktrees GET https://markdownregistry.com/api/v1/blob/2a44fd4524f455f1ceb2434f499daeee70a17f1d8e8a4c1ba69b0901802a8550
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.