Show HN: AISlop, a CLI for catching AI generated code smells

github.com

29 points by Heavykenny 43 minutes ago

Hi, I’m Kenny, I’ve been building aislop. I starting working on this after using Claude Code, codex and opencode several times and noticing some slops. They aren’t syntax and passes most tests, they are patterns like empty catch blocks, useless comments, duplicated helpers, dead code and many more. So I built a tool to scan and check for these patterns and wired it into hooks so after each tool call, the agent checks for the slops.

You can try it out with npx aislop scan.

It’s all local and no code is transferred. Thank you.

bigfishrunning - 24 minutes ago

A linter with rules for AI-specific weirdness is absolutely a great idea, thank you! Are there any plans to support other languages besides javascript?

maddhruvhn - a minute ago

awesome work, someone is caring about using less token :clap:

sync - 2 minutes ago

I tried it on my codebase. There's a lot of overlap with tools like Oxlint / ESLint, I'm not sure that's too valuable vs. a more focused tool that actually focuses solely on 'slop' signals. These lint rules tend to get very opinionated which is why those tools expose so many configuration options.

One real bug tho:

> [ERROR] Imports "mdast" but it's not declared in package.json

A type-only import like `import type { Blockquote, RootContent } from 'mdast';` is actually acceptable if `"@types/mdast": "^4.0.4"` is included in the package.json.

throw03172019 - 14 minutes ago

> I’ve been building aislop.

This made me chuckle.

Cool tool, the dead code checks can be very helpful. I’ve seen Claude leave unused functions when iterating which always frustrates me.

eithed - 6 minutes ago

Can you explain the benefits of running this over rector / eslint? (and to certain degree phpstan / deptrac)

hootz - 33 minutes ago

Ran it in my codebase, detected some good stuff, was able to pass the issues to my agent so they can be validated and fixed. Good job!

I'd love for it to have flags for Pi and Crush too :)

Der_Einzige - 21 minutes ago

Related, we made "Antislop", a framework for removing repetitive phraseology from LLMs: https://arxiv.org/abs/2510.15061

cumshitpiss - a minute ago

[dead]

pixel_popping - 22 minutes ago

The intent is good, but frankly, credibility is lost by using "slop" words imo, OP you might seriously want to re-evaluate who is the target market, probably users that leverage high automation 24/7, startups and so-on, they don't want to incorporate products that talks about the modern way (and somehow only way to compete) of development as "slop" imo because soon enough, it's not true anymore (it's already not true with the right tooling).

axod - 26 minutes ago

I don't think this approach is wise.

Concentrate on code quality, and whether it does what it needs to do. Not whether it was written by AI or not.