cleanup
Skill0 starsChanged 9 days agoMITView on GitHub
Finds the worktrees, local branches, remote branches and pull requests that past work left in a repository, removes the ones that are safe to remove, and reports the others. Use when the user asks to clean up, tidy or prune branches, worktrees or PRs, or says that a repository has too many of them.
- Commits and pushes
71 other projects use a version of this.
Adopted by
Most recently taken up by
- udecode/better-convextheir own version, first seen Nov 9, 2026
- fynnhaupt/skillstheir own version, first seen Nov 8, 2026
- VforVal/lumberjacktheir own version, first seen Nov 8, 2026
- LeonardiFranco/skillstheir own version, first seen Nov 8, 2026
- frnkgns/Overgeared-Skillstheir own version, first seen Nov 8, 2026
- Integralist/agent-skillstheir own version, first seen Nov 6, 2026
Used with
Projects with it also use chips, react-query-best-practices and 10 more.
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.
udecodeSkillchips
Run the project's suggested-task ledger, the chips. /chips alone brings this session's open tasks up to date: it applies what the ledger helper says, settles stale and split tasks, cards what can start and reports the board, and /chips all also takes the ship-list tasks and the ones no live session owns, and merges duplicate tasks across the board. Use for /chips, /chips offer, start or drop, \"what chips are open\", \"suggest a task for X\", \"update the chips\", \"clean up the chips\", \"which chips are stale\", \"is this chip still worth doing\", \"merge duplicate chips\", at the last hand-back of a run that offered a task, and whenever pstack would file a tracked issue, a follow-up, a reflect Backlog item or an out-of-band PR.
Also in 3 projects that use this
bibektimilsina00Skillreact-query-best-practices
Audit and fix React Query usage in apps/web — enforce query key factories, signal forwarding, staleTime, and proper mutation patterns. Use when reviewing or fixing server-state code.
Also in 3 projects that use this
- bibektimilsina00Skill
you-might-not-need-a-callback
Analyze and fix useCallback anti-patterns in your code
Also in 3 projects that use this
Scylla23Skillredo
Re-run the last routed task one model tier up (haiku → sonnet → opus → fable). User-invoked escalation when the previous result missed. Pass --dry-run to preview without running.
Also in 3 projects that use this
Aetheria-Labs1Skillplan-page
Plan one storefront page from strategy through final copy, section order, proof, offers, template direction, responsive layout, and production asset requirements. Stops at an approved execution-ready specification.
Also in 3 projects that use this
SocialKit-APISkillvideo-transcripts
Extract transcripts from social videos through SocialKit across YouTube, TikTok, Instagram, Facebook, X/Twitter, LinkedIn, and direct video file URLs. Use when the user asks to transcribe, get captions or subtitles, pull the spoken text, or read what a video says, including one video or many at once. Returns full text plus timestamped segments. Not for posting, private accounts, or unrelated website scraping.
Also in 3 projects that use this
- +3 more from bibektimilsina00
Other versions71 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 71
- simstudioai/sim★ 30ksame name
- pipecat-ai/pipecat★ 17ksame name
- udecode/plate★ 17ksame name
- civitai/civitai★ 7.3ksame name
- mampfes/hacs_waste_collection_schedule★ 2.3ksame name
- trycompai/comp★ 2.1ksame name
- udecode/dotai★ 1.2ksame name
- LedgerHQ/ledger-live★ 627same name
- ericboy0224/learn-docker-and-k8s★ 472same name
- udecode/better-convex★ 452same name
61 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.
In this repository24 other files it gives its agents.
- AGENTS.mdAGENTS.md
- rules/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- babysit-prSkill
- beast-uiSkill
- councilSkill
- doc-viewSkill
- featuremapSkill
- file-prSkill
- frontend-designSkill
- full-sendSkill
- full-stopSkill
- impeccableSkill
- leaving-pr-commentsSkill
- modernizeSkill
- no-commentsSkill
- patrolSkill
- sol-loopSkill
- statechartSkill
- technical-writingSkill
- tldrSkill
- untangleSkill
- verify-prSkill
- whySkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 61 edited versions we read keep these.
3
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
- Distinctive: line 8
Remove what past work left in a repository.
- Distinctive: line 40
Never remove the default branch, the current branch, the main worktree or the worktree that you run in.
- Very specific: line 54
If delete_branch_on_merge is false, tell the user.
- Distinctive: line 56
Run it only when the user asks, because it changes a repository setting.
“Common” is measured: kept by at least 6 in 10 of the 61 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
Cleanup
Remove what past work left in a repository. Remove only the items that are safe to remove. Report each other item with the reason that you kept it. This skill is the permission to delete the safe items.
1. Collect
Change nothing in this step. Run:
git worktree list --porcelaingit branch --format='%(refname:short) %(objectname:short) %(upstream:short) %(upstream:track)'git ls-remote --heads origingh pr list --state all --limit 300 --json number,state,author,headRefName,updatedAt,urlgh api repos/{owner}/{repo} --jq .delete_branch_on_mergegit stash list
The two gh commands are for GitHub. On another forge, use its CLI or API for
the same step. Find the forge from the PR URL, the remote URL, the CI files and
the signed-in CLIs. Collect the same fields.
A squash merge does not make the branch an ancestor of the default branch. So
use the state of the PR to find merged work, not only git branch --merged.
2. Classify
| Item | Safe to remove when | Keep and report when |
| Worktree | Its branch has a merged or closed PR, or the default branch contains it, and git status --porcelain in it prints nothing. | git status --porcelain in it prints a line, which includes untracked files, or it has an open PR, or a session uses it now. |
| Local branch | Its PR merged or closed, or the default branch contains it, and each of its commits is on the remote. | It has commits that are on no remote. |
| Remote branch | Its PR merged, or its PR closed and you are the author. | It has an open PR or no PR, or another person closed it. |
| Pull request | Never in this skill. | It had no update for 30 days, or a newer PR replaces it. |
| Stash | Never in this skill. | Always. Other worktrees share the stash list. |
Never remove the default branch, the current branch, the main worktree or the
worktree that you run in. Take each path from git worktree list. Do not type
a path by hand.
3. Remove the safe items
- Worktree:
git worktree remove <path>, thengit worktree prune. Do not use--force. - Local branch: record its SHA, then run
git branch -D <name>. - Remote branch:
git push origin --delete <name>. - Stale tracking refs:
git fetch --prune origin.
4. Find the cause
If delete_branch_on_merge is false, tell the user. Give this command to
turn it on: gh api -X PATCH repos/{owner}/{repo} -f delete_branch_on_merge=true.
Run it only when the user asks, because it changes a repository setting. On
another forge, find the same setting. If the forge has no such setting, skip
this step.
Report
- Each item that you removed. For each local branch, give its SHA, so that
git branch <name> <sha>can restore it. - Each item that you kept, with its reason.
- Each stash, with its message.
- Each open PR that is stale or replaced, with its link and your recommendation.
- On GitHub, a remote branch of a merged or closed PR can come back from the PR page.
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.