Unslop

The code-side counterpart to deslop. Same instinct, different material: deslop takes the tells out of writing, unslop takes them out of code.

Agent-written code carries a signature. Not bugs - it typechecks, the tests pass, it works. It is padded with ceremony that exists because a model was being thorough rather than because anything needs it, and the cost lands on whoever reads it next.

The rule that decides every call: nothing here changes behaviour. Remove a tell and the tests still pass unchanged. If a cleanup would alter what the program does, it is not this skill's - a fallback that hides a failure belongs to fail-fast, a file too big to hold in your head belongs to componentize. Say so and move on rather than smuggling a behaviour change into a tidy-up.

Read the surrounding code before calling something a tell. Local conventions and the purpose of an abstraction matter: a one-caller wrapper can still name a meaningful operation or preserve a useful boundary. The catalogue gives you patterns to investigate, not automatic deletions. Prefer the smallest edit that removes confirmed noise; do not rewrite neighbouring code to match your taste.

The tells

Cite by number in findings, so a reviewer can see the pattern rather than the instance.

Comments and names