awesome-slop-auditlisted

# AI Slop Audit This skill reads and reports. It never edits. Every fix its findings call for — the comment rewrite, the rename, the drift-pair unification, the CI template extraction — is executed by `awesome-code-cleanup`, which owns the editing bar, the behavior-preserving proof and the regression gate. Splitting it this way is what lets the catalog below range over docs and CI without a second skill rewriting the same line. A slop marker is anything that makes a reader think "a machine wrote this and nobody read it". Three classes, in descending order of harm: 1. Lies — statements the code disproves: a comment claiming "three use sites" over five, a README documenting a 15s default the code sets to 13s, a rationale explaining a mechanism that no longer exists. Highest value: these mislead the next reader every day they survive. 2. Noise — formulaic filler: narration comments, echo-JSDoc, banner rows, template comments stamped verbatim across sibling files, copy-pasted test strophes, an 8-step CI setup block pasted into 7 jobs. 3. Fingerprints — uniform stylistic tics: typographic glyphs where a keyboard author would type ASCII, em-dash saturation, "X, not Y" contrast in every third config comment, bold-lead + emoji bullet lists, rule-of-three phrasing. The core discipline: verify before flagging, and prove absence to yourself too. Dense commentary is not slop — a comment that checks out against the code (recount the constant, re-derive the number, grep the callers) is