agentleFS
Sign inStart free
nodealchemynodealchemy/powernode-platform/.claude/skills/cleanup/SKILL.md

cleanup

Skill4 starsChanged 18 days agoMITView on GitHub

Run codebase cleanup and validation scripts. Wraps existing automation scripts into a single command. Based on the argument (default: all), run the appropriate scripts: After cleanup, run quality gates: If TypeScript errors are introduced by cleanup, fix them before reporting completion.

71 other projects use a version of this.

Adopted by

Most recently taken up by

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.
  • 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. 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

  • bibektimilsina00Skill

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

  • 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

5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 61 edited versions we read keep these.

  • 4

    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
  1. Distinctive:

    Run codebase cleanup and validation scripts.

    line 3
  2. Distinctive:

    Run the selected script(s) from the project root

    line 33
  3. Very specific:

    If all mode, run in this order:

    line 35
  4. Distinctive:

    After cleanup, run quality gates:

    line 44
  5. Distinctive:

    If TypeScript errors are introduced by cleanup, fix them before reporting completion.

    line 49

“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.

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

/cleanup — Codebase Cleanup

Run codebase cleanup and validation scripts. Wraps existing automation scripts into a single command.

Usage

/cleanup              # Run all cleanup checks
/cleanup console      # Remove console.log statements
/cleanup patterns     # Run pattern validation audit
/cleanup colors       # Fix hardcoded color violations
/cleanup imports      # Convert relative imports to path aliases
/cleanup quick        # Quick pattern check only

Workflow

Determine Scope

Based on the argument (default: all), run the appropriate scripts:

ArgumentScriptDescription
allAll scripts below in orderFull cleanup pass
console./scripts/cleanup-all-console-logs.shRemove console.log from frontend
patterns./scripts/pattern-validation.shFull pattern audit (colors, imports, types)
colors./scripts/fix-hardcoded-colors.shReplace hardcoded colors with theme classes
imports./scripts/convert-relative-imports.shConvert relative imports to @/ aliases
quick./scripts/quick-pattern-check.shFast pattern check

Execution

  1. Run the selected script(s) from the project root
  2. Capture output and report results
  3. If all mode, run in this order:
    1. ./scripts/cleanup-all-console-logs.sh
    2. ./scripts/fix-hardcoded-colors.sh
    3. ./scripts/convert-relative-imports.sh
    4. ./scripts/pattern-validation.sh
  4. Report summary of changes made and any remaining issues

Post-Cleanup Verification

After cleanup, run quality gates:

cd frontend && npx tsc --noEmit    # Verify no TypeScript errors introduced

If TypeScript errors are introduced by cleanup, fix them before reporting completion.

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.

Check your setup, free