worktree-cleanup
Skill1 starsChanged 52 days agoNo licenceView on GitHub
Clean up merged git worktrees and their local branches. Use this skill whenever the user wants to clean up worktrees, prune stale worktrees, remove merged worktrees, tidy up their worktree list, or asks anything about cleaning up after merged branches in a worktree-based workflow. Also trigger when the user says things like "clean up worktrees", "remove old worktrees", "which worktrees can I delete", "prune merged branches", or "tidy up my git worktrees". If the user works with git worktrees and mentions cleanup or pruning, this skill applies.
- Deletes or force-pushes
10 other projects use a version of this.
Adopted by
Most recently taken up by
- anotherben/claude-harnesstheir own version, first seen Nov 8, 2026
- perber/leafwikitheir own version, first seen Oct 17, 2026
- my-chiefmind/ai-maestrotheir own version, first seen Oct 13, 2026
- TentacleOpera/switchboardtheir own version, first seen Oct 8, 2026
- syanga/astacktheir own version, first seen Sep 20, 2026
- Jador/skillstheir own version, first seen Aug 27, 2026
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 10
- perber/leafwiki★ 1.2ksame name
- TentacleOpera/switchboard★ 215same name
- anotherben/claude-harness★ 7same name
- my-chiefmind/ai-maestro★ 6same name
- Jador/skills★ 1same name
- jelbirt/LLM-Skill-Build★ 1same name
- luw2007/skills★ 1same name
- EdenGibson/claude-skills★ 0same name
- Enverge-Labs/skills★ 0same name
- syanga/astack★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository12 other files it gives its agents.
- AGENTS.mdAGENTS.md
- dev-preferencesSkill
- github-reviewSkill
- go-devSkill
- grillingSkill
- handoffSkill
- hindsightSkill
- miseSkill
- peer-consultSkill
- plain-englishSkill
- tmuxSkill
- ttsSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 3 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 10 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 10 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.