cleanup
Skill2 starsChanged 2 months agoMITView on GitHub
Safely close a completed or paused task by verifying owned disposable state, preserving recoverable leftovers, and producing a truthful handoff. Use when a branch, worktree, slot, browser session, loop, or temporary artifact may need cleanup.
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 repository19 other files it gives its agents.
- access-checkSkill
- babysit-prsSkill
- browser-proofSkill
- bugfixSkill
- bug-reproSkill
- contextSkill
- dev-flowSkill
- docs-managerSkill
- hot-reloadSkill
- jira-managerSkill
- polishSkill
- pr-managerSkill
- release-proofSkill
- status-reportSkill
- sync-projectSkill
- watch-loopSkill
- whatsapp-meSkill
- workflowSkill
- worktreeSkill
The file
We split this skill into the rules it gives an agent
12 rules. 0 are common, 10 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 61 edited versions we read keep these.
10
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Do not delete dirty, ambiguous, or unowned state just to make the workspace look clean.
- Distinctive: line 17
Before removing anything, list the task-owned state:
- Very specific: line 33
Only owned-and-clean is eligible for automatic removal.
- Distinctive: line 39
Verify git state before removing a worktree or branch.
- Distinctive: line 40
Stop slots, port-forwards, or browser state only when they are clearly owned.
- Distinctive: line 46
Never remove the main or canonical checkout.
- Distinctive: line 47
Never remove a dirty worktree without explicit authority and a recovery plan.
- Distinctive: line 48
Do not assume a branch is disposable because its remote disappeared.
- Distinctive: line 54
Stop only task-owned slots, containers, native processes, watchers, and port forwards.
- Distinctive: line 57
Remove test records through the product or API path first when normal cleanup hooks matter.
- Distinctive: line 58
Keep screenshots, logs, and evidence that are still required for review, audit, or resume.
- Very specific: line 60
If cleanup fails after the feature proof passes, the task is still blocked on cleanup.
“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
Cleanup is part of the workflow, not an afterthought.
Core Rule
Do not delete dirty, ambiguous, or unowned state just to make the workspace look clean.
Cleanup Ledger
Before removing anything, list the task-owned state:
- branch
- worktree
- slot or local app processes
- browser session or temporary auth state
- temporary data, screenshots, logs, or exports
- loops, watchers, or port-forwards
Mark each item as:
owned-and-cleanowned-but-dirtyunknown-owneralready-gone
Only owned-and-clean is eligible for automatic removal.
Workflow
- Record the task label and intended stop state.
- Build the cleanup ledger.
- Verify git state before removing a worktree or branch.
- Stop slots, port-forwards, or browser state only when they are clearly owned.
- Preserve evidence that is still useful for resume or audit.
- Report every leftover plainly.
Worktree And Branch Rules
- Never remove the main or canonical checkout.
- Never remove a dirty worktree without explicit authority and a recovery plan.
- Do not assume a branch is disposable because its remote disappeared.
- Recheck status, ownership, and open PR or MR state immediately before removal.
- Prune git metadata only after owned removals are complete.
Runtime And Browser Rules
- Stop only task-owned slots, containers, native processes, watchers, and port forwards.
- A slot stop must not stop shared warm infrastructure.
- Close task-owned browser sessions and temporary auth state.
- Remove test records through the product or API path first when normal cleanup hooks matter.
- Keep screenshots, logs, and evidence that are still required for review, audit, or resume.
If cleanup fails after the feature proof passes, the task is still blocked on cleanup. Do not hide residual resources behind a success message.
Output Contract
CLEANUP | task=<label> | status=<closed|paused|blocked>
REMOVED | <items or none>
LEFTOVERS | <dirty, unknown, shared, or intentionally preserved items>
PROOF | <git, process, browser, or data cleanup result>
RESUME | <none or exact next step>Stop Conditions
Return closed only when every owned disposable item is removed or intentionally preserved with a reason. Return paused when the state is ready to resume. Return blocked when dirty, unknown, shared, or failed cleanup remains.
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.