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

Posted by Heavykenny 3 hours ago

Show HN: AISlop, a CLI for catching AI generated code smells(github.com)

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.

63 points | 54 commentspage 3

pixel_popping 3 hours 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).

trollbridge 2 hours ago||

Imagine an operating system company making a product called “quick and dirty”.

hootz 3 hours ago||

Yeah, to be honest, it really is a bit weird to incorporate a tool called slop into a corporate CICD flow. Anubis fixed a similar problem by creating a corp-safe version without the anime mascot.

Aurornis 3 hours ago||

> Anubis fixed a similar problem by creating a corp-safe version without the anime mascot.

I wouldn’t say they fixed it. Rather it was an intentional choice to put an anime girl on websites unless you paid for the product.

hootz 2 hours ago||

Fair, I guess that doesn't apply here then, as I don't think the intention of OP is to drive corps away from the main free product.

axod 3 hours 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.

Heavykenny 3 hours ago||

Thanks, I actually concentrated on improving code quality, the patterns I flagged are poor design choices that humans wouldn’t write. Examples are duplicated functions doing same thing, dead or redundant codes etc. These builds up and degrade the codebase over time.

axod 3 hours ago||

> ...are poor design choices that humans wouldn’t write.

They certainly do in my experience. Maybe you've been lucky and haven't worked with really messy programmers.

Heavykenny 3 hours ago||

I have worked and seen these in code reviews but the issue now is code reviews are overwhelming and non existent in some cases.

bigfishrunning 3 hours ago||

I'm interpreting this not as a "catch ai submissions gotcha" tool, but as a "last pass in review catch mistakes AI made that i may have missed" tool. Having more linters is a good thing IMO (I say this as someone who doesn't use AI to generate code, but works with people who do and has to review a lot of AI generated code)

tolawuwo 2 hours ago||

Exactly, that’s what it does. You can see the tool as a quality gate you put in place to ensure that any AI generated code meets a standard.