Run all 8 cleanup skills in sequence: unused → cycles → dedupe → types → weak-types → defensive → legacy → slop. Each step verifies before the next runs; halts on first failure. Produces one consolidated report. Use when the user asks to clean up the whole codebase, run all cleanup skills, do a full code-quality pass, or sweep the repo. Example queries — "clean up the whole codebase", "run a full code-quality pass", "sweep this repo", "do all the cleanups in order".
Run all 8 cleanup skills in sequence: unused → cycles → dedupe → types → weak-types → defensive → legacy → slop. Each step verifies before the next runs; halts on first failure. Produces one consolidated report. Use when the user asks to clean up the whole codebase, run all cleanup skills, do a full code-quality pass, or sweep the repo. Example queries — "clean up the whole codebase", "run a full code-quality pass", "sweep this repo", "do all the cleanups in order".
argument-hint
[scope (optional path or glob)]
user-invocable
true
Orchestrate the full cleanup pipeline. Runs each of the 8 cleanup skills in a deliberate order chosen so each step shrinks the surface for the next. Halts on first verify failure so you can investigate before the cascade continues.
Preflight
Confirm intent: this will produce up to 8 separate commits and may touch many files. Show the user the planned order and ask confirmation if the working tree has any commits ahead of the upstream branch (might compound with their unpushed work).
Git state: refuse on dirty working tree. Each child skill needs a clean baseline for its verify step.
Create master report: .claude/cleanup-reports/cleanup-all-{YYYY-MM-DD}.md — child skill reports will be linked from this.
Estimate baseline: capture LOC, file count, dependency count, knip findings, madge cycles count, weak-type count. Used for before/after comparison at the end.
Execution Order
Each child skill is invoked via Skill tool. After each, run that skill's verify step. Halt the pipeline on any verify failure — do not proceed to the next step.
cleanup-unused — delete dead code first. Less for everything downstream to scan.
cleanup-cycles — fix the dependency graph next. Other refactors are safer in an acyclic graph.
cleanup-dedupe — extract duplicates. Now that dead code is gone and graph is clean, real duplicates surface.
cleanup-types — consolidate types. Often dedupe surfaces type duplication too.
cleanup-weak-types — strengthen types. Easier with consolidated type modules in place.
cleanup-defensive — remove pointless try/catch. Type strengthening sometimes makes catches obviously wrong.
cleanup-legacy — remove deprecated/fallback. Type changes may have already revealed dead branches.
cleanup-slop — strip unhelpful comments last. Cosmetic, no logic change.
Why this order
Destructive then constructive then cosmetic. Deletion first reduces what later skills consider.
Structure before contents. Cycles and unused are graph-level; dedupe and types are content-level; slop is line-level.
Riskiest reversible-changes early when the diff is small and the human can review faster. Slop last because it's safest and produces the largest comment diff.
Each step's commit is a clean revert point if the user wants to undo a single phase.
Per-step protocol
For each skill in order:
Print: ▶ Running cleanup-X (step Y/8)…
Invoke the skill via the Skill tool with the same scope arg (if any).
Wait for the skill to finish — it produces its own commit and verify result.
If the skill's verify failed: HALT, print ✗ cleanup-X verify failed — halting pipeline. See report at <path>.
If verify passed: append findings count + LOC delta to master report, continue.
