cleanup-slop

Surgically remove unhelpful comments without touching code. The good comments — workarounds, invariants, citations, non-obvious WHYs — stay. The bad ones — restating code, narrating in-motion edits, AI-generated platitudes — go. **Core rule**: a useful comment tells a future reader something they couldn't get by reading the code itself. Everything else is noise. ## Preflight 1. **Language detect** — comment syntax differs but the patterns are universal. 2. **Git state**: refuse on dirty tree. 3. **Report dir**: ensure exists. 4. **No code changes**: this skill ONLY edits comments. If a "comment fix" requires changing code, surface to user instead. ## Detect Use grep + heuristics. There's no perfect tool — this is mostly pattern matching. ### Patterns to find (HIGH-confidence slop) **A. Restated-code comments** — comment says what the code already says. ```bash # Look for comments immediately above a line where the comment is essentially the function/variable name in English grep -rn --include="*.ts" --include="*.tsx" --include="*.py" --include="*.js" \ -B0 -A1 -E "^\s*(//|#) (Returns|Sets|Gets|Creates|Updates|Deletes|Removes|Adds|Imports|Exports|Initializes|Initialize|Render|Renders) " . > /tmp/restated.txt ``` **B. In-motion narration** — comments describing the edit, not the code. ```bash grep -rn --include="*.ts" --include="*.tsx" --include="*.py" --include="*.js" --include="*.go" --include="*.rs" \ -E "(// |# )(removed|replaced|new approach|updated to|previous...