Deslop
Hacker ApprovedRanked 8 of 14 linters by recommenders
Free tool that cleans up sloppy AI-generated code and front ends, which people find useful for LLM output.
Free tool that cleans up sloppy AI-generated code and front ends, which people find useful for LLM output.
11 people gave an opinion
- recommend it
- 10
- criticize it
- 1
- approval share
- 91%
Recommended in 5 of 13 months
- November 2025: not recommended
- December 2025: not recommended
- January 2026: not recommended
- February 2026: not recommended
- March 2026: not recommended
- April 2026: recommended
- May 2026: not recommended
- June 2026: recommended
- July 2026: recommended
- August 2026: recommended
- September 2026: not recommended
- October 2026: recommended
- November 2026: not recommended (month in progress)
Why it carries the badge
- 10 people recommend itNeeds 10 or more, met.
- 10 recommenders for every criticNeeds 2 to 1 or better, met.
- Recommended in 5 of 13 monthsNeeds 4 or more, met.
The same three rules apply to every product, and the badge can’t be bought. How the badge works
What people say about it
The reasons people give, with the number of comments that give each one. Open a reason to read what they said.
Why people recommend it
Each mark is one comment
Cleans up sloppy AI-generated code
“I invoke it to clean up Claude output when it goes off the rails.”
Comment from 20 Aug 2026 in “Clean up Claude 5's token vomit with a separate LLM” “I've started adding to my friends sloppy codebases and its great!”
Comment from 13 Oct 2026 in “Show HN: Deslop – Oxlint rules for AI-generated TypeScript” Good rules improve LLM output
“I really believe having good rules like this can make a big difference in llm quality.”
Comment from 13 Oct 2026 in “Show HN: Deslop – Oxlint rules for AI-generated TypeScript” “no-reflect-get is definitely one I'd adopt”
Comment from 13 Oct 2026 in “Show HN: Deslop – Oxlint rules for AI-generated TypeScript” Convenient, usable, not sloppy-looking
“That's refreshingly usable and not-slop-looking, nice additional style.”
Comment from 12 Jun 2026 in “Slightly reducing the sloppiness of AI generated front end” “This just makes it super convenient.”
Comment from 14 Oct 2026 in “Show HN: Deslop – Oxlint rules for AI-generated TypeScript”
What people warn about
Each mark is one comment
Output still a bit smelly
“It's still a little smelly imo, but better.”
Comment from 23 Jul 2026 in “Launch HN: Unlayer (YC W22) – Add email and document builders to your app”
Other linters people recommend
The four most recommended other linters, with the same counts for each, so you can compare like for like. The tick on each bar marks the 2 to 1 line the badge needs.
| Product | Recommend | Criticize | Approval | Months | Owned | Badge |
|---|---|---|---|---|---|---|
| Ruff | 115 | 16 | 88% | 11 | — | Approved |
| Clippy (Rust linter) | 58 | 31 | 65% | 12 | — | — |
| ESLint | 32 | 22 | 59% | 11 | — | — |
| Biome | 23 | 5 | 82% | 10 | — | Approved |
| DeslopThis page | 10 | 1 | 91% | 5 | — | Approved |
What people said
11 of the 12 comments that mention it, newest first. Each links to the original comment.
“The q4 loops after 16k tokens generated.”
“This just makes it super convenient.”
“no-reflect-get is definitely one I'd adopt”
“I've started adding to my friends sloppy codebases and its great!”
“I really believe having good rules like this can make a big difference in llm quality.”
“I invoke it to clean up Claude output when it goes off the rails.”
“I wrote a simple tool for it as part of my CI”
“It's still a little smelly imo, but better.”
“That's refreshingly usable and not-slop-looking, nice additional style.”
“here's an interesting list of their quirks”
“It looks like a method of fabricating more convincing slop?”
Counts come from 1,795,640 Hacker News comments, November 2025 to November 2026. How we count. Report a mistake.