cleanuplisted

# Cleanup Losslessly reorganize a messy notes/plan/chat dump into a clean sectioned markdown file, with three-level gap detection to prove nothing was lost. > **Letter = spirit.** If a rule blocks you from reaching the goal it was > written for, the rule is wrong, not the goal. Don't look for a wording > loophole — ask what the rule is protecting, and protect that. ## Usage ``` /cleanup <file> [file2] [file3] ... ``` Multi-file: each input is processed independently end-to-end. Output is N cleaned files, NOT one merged file. (Opt-in `--merge` flag preserves legacy single-output behavior for back-compat.) ## Weaknesses and when NOT to use - **Slow and thorough — overkill for short files.** If the file is already structured with `## ` sections and shorter than 30 lines, manual editing is faster. - **Context cost grows linearly with input size.** Phase 4 (gap detection) spawns background agents on large files — watch your budget. For files >2000 lines, consider splitting the input. - **Does not work with non-markdown formats.** JSON/YAML/code dumps — use a different tool. - **Does not extract content from links** (YouTube, Telegram). For that, run `/extract` before `/cleanup`. - **Does not summarize.** This skill is preservation-first; if you want to shrink ideas, use a different tool (e.g. `mattpocock:to-prd` for PRD-style summarization). ## How to do it wrong vs right ### Multi-file input ❌ **Wrong:** 3 input files → concatenate into one merged file with `<!-- from: