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

#1

Post by Heavykenny » Fri, May 29, 2026, 1:37 PM UTC

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.

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

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

#2

Post by hootz » Fri, May 29, 2026, 1:47 PM UTC

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 :)

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

#3

Post by axod » Fri, May 29, 2026, 1:54 PM UTC

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.

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

#4

Post by bigfishrunning » Fri, May 29, 2026, 1:56 PM UTC

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?

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

#5

Post by bigfishrunning » Fri, May 29, 2026, 1:58 PM UTC

axod wrote: post #3

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.

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)

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

#6

Post by pixel_popping » Fri, May 29, 2026, 1:58 PM UTC

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).

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

#7

Post by Der_Einzige » Fri, May 29, 2026, 1:59 PM UTC

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

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

#8

Post by Heavykenny » Fri, May 29, 2026, 1:59 PM UTC

axod wrote: post #3

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.

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.

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

#9

Post by axod » Fri, May 29, 2026, 2:01 PM UTC

Heavykenny wrote: post #8

axod wrote: post #3

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.

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.

> ...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.

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

#10

Post by hootz » Fri, May 29, 2026, 2:02 PM UTC

pixel_popping wrote: post #6

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…

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.