git-cleanup
Skill0 starsChanged 17 days agoMIT-0View on GitHub
Use when local git worktrees or branches have piled up in a checkout of this repository and the person wants to tidy them, such as "clean up old branches", "remove merged worktrees", "what can I delete in .claude/worktrees", or after a batch of pull requests merges. Runs the dry-run cleanup script, shows what it would delete, and leaves the deletion and any remote-branch deletion to the person.
- Commits and pushes
11 other projects use a version of this.
Adopted by
Most recently taken up by
- UlyssesLeoLee/MAGOStheir own version, first seen Nov 4, 2026
- bryanus1/agent-skillstheir own version, first seen Nov 1, 2026
- tanuuuuuuu/dotfilestheir own version, first seen Oct 20, 2026
- davidanthonyn/claude-skillstheir own version, first seen Oct 20, 2026
- InanisV/my-claude-skillstheir own version, first seen Aug 22, 2026
- alibaba/page-agenttheir own version, first seen Jul 17, 2026
Used with
Projects with it also use skill-creator.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
SentrySkillskill-creator
Create new agent skills following the Agent Skills specification. Use when asked to "create a skill", "add a new skill", "write a skill", "make a skill", "build a skill", or scaffold a new skill with SKILL.md. Guides through requirements, writing, registration, and verification.
Also in 4 projects that use this
Other versions11 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 11
- alibaba/page-agent★ 29ksame name
- viknesh20-20/claude-code-tool-kit★ 7same name
- InanisV/my-claude-skills★ 1same name
- UlyssesLeoLee/MAGOS★ 1same name
- bryanus1/agent-skills★ 0same name
- CarpeWu/claude-git-skills★ 0same name
- davidanthonyn/claude-skills★ 0same name
- linnene/Code-Standards-Skills★ 0same name
- tanuuuuuuu/dotfiles★ 0same name
- TheWatcher01/skills★ 0same name
1 more not listed
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.
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 8 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 21
Run the dry run, make git-cleanup, and show its whole output: the DELETE and KEEP lines, the unmerged commits, the remote list, and any …
- Distinctive: line 25
After they run it, run the dry run again and report what is left.
“Common” is measured: kept by at least 6 in 10 of the 8 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.
Files
Clean Up Merged Branches and Worktrees
Canonical doc: docs/local-development.md ("Git Housekeeping"). Read it before running anything. This skill gives the order of the steps and holds no rules of its own.
What you decide
These stay with the person; ask, do not choose:
- whether to run
--executeafter reading the dry run; - whether any unmerged branch can be dropped with
--include-unmerged; - whether to delete the remote branches the script lists.
Steps
- Fast-forward
mainfirst, so "in origin/main" reflects what has merged. - Run the dry run,
make git-cleanup, and show its whole output: the DELETE and KEEP lines, the unmerged commits, the remote list, and any note that open pull requests were not checked. - For each unmerged branch, say what its commits are and whether they reached
mainanother way (for example, a squash merge, or a pull request merged into another branch instead ofmain). Do not call a branch safe to drop without that check. - For a worktree kept for uncommitted changes, compare those changes with
mainand report the result; do not discard them. - Give the person the commands to run:
make git-cleanupwithGIT_CLEANUP_ARGS=--execute(and--include-unmergedonly if they chose it), and the printedgit push origin --deleteline for remote branches. They run these themselves, for example with!in the Claude Code prompt. - After they run it, run the dry run again and report what is left.
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.

