agentleFS
darrenCWJdarrenCWJ/agent-skills-scaffold/.claude/skills/cleanup/SKILL.md

cleanup

Skill0 starsChanged 3 months agoMITView on GitHub

Remove work debris and resolve loose ends before shipping. Use in the ship phase of every M/L task, after loops conclude, when the user says clean up or tidy, or when temp files, debug residue, stale TODOs, or unexplained ledger rows have accumulated. Always runs BEFORE final-check.

79 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use chips, you-might-not-need-a-callback 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.
  • udecodeSkill

    chips

    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. /chips sync runs the same sweep but offers no card, and it moves the waits on plans idle for a week to a fresh verdict. Use for /chips, /chips sync, /chips offer, start or drop, \"update the chips without new cards\", \"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

  • bibektimilsina00Skill

    you-might-not-need-a-callback

    Analyze and fix useCallback anti-patterns in your code

    Also in 3 projects that use this

  • bibektimilsina00Skill

    you-might-not-need-a-memo

    Analyze and fix useMemo/React.memo anti-patterns in your code

    Also in 3 projects that use this

  • Scylla23Skill

    redo

    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-Labs1Skill

    plan-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-APISkill

    video-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

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 67 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    After cleanup, re-run the primary verification once — cleanup breaks things more often than anyone expects.

    line 28

“Common” is measured: kept by at least 6 in 10 of the 67 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Cleanup

Debris compounds. Every task ends with a cleanup pass BEFORE the final check — never after (cleanup can break things; the final check must see the true final state).

Sweep list

  1. Temp artifacts — scratch files, debug outputs, test2_final_v3 files, downloaded intermediates, probe files. Delete or move to an explicit scratch/ that's gitignored.
  2. Dead work — code paths, doc sections, or plan branches abandoned mid-task. Remove them; the design-decision record (not commented-out corpses) preserves the history.
  3. Debug residue — print/log statements, hardcoded test values, commented-out experiments, verbose flags left on.
  4. TODOs — every TODO you introduced: either do it now (< 5 min), convert it to a task-list item / plan future-work entry, or delete it. No orphan TODOs.
  5. Naming and placement — files where they belong per repo structure, names that describe contents, no untitled / new / copy.
  6. The ledger — reconcile the diff-management change ledger: every row accounted for, every In plan? = no row resolved (amended or reverted).
  7. Docs drift — README/docs statements invalidated by this task's changes get fixed now, not "later".
  8. Task list — close finished items, delete stale ones, ensure remaining items are real future work.

Issue triage (loose ends found during cleanup)

For each open issue discovered: fix now if < 5 minutes AND in scope; otherwise record it (task list + handover Landmines section) with enough context that future-you doesn't have to rediscover it. The worst outcome is a known issue that becomes unknown again.

Rules

  • Cleanup never adds features. If you feel the urge, task-list it.
  • Cleanup changes go through the same diff discipline (ledger rows, committed separately as cleanup: if in git).
  • After cleanup, re-run the primary verification once — cleanup breaks things more often than anyone expects.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.