vibe-clean

# /vibe-clean

Take a code surface — by default the current branch's diff against `main` — and clean it up. The methodology proceeds in this order: **establish a comprehension baseline first** (characterization tests on real inputs; run-and-observe rather than read-and-believe), then **verify dependencies are real** (no hallucinated imports; no slopsquatting), then **trace every abstraction to its callers** and inline what doesn't earn its keep. Default deletion-first. Grounded in [`.research/code-simplification.md`](../.research/code-simplification.md) §6 and §8.5.

The defining commitment of the skill is **comprehension before structure**. Plausible-looking code is the failure mode; reading it is not enough; running it on real inputs is the source of truth.