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

Post by pella » Fri, May 29, 2026, 7:47 PM UTC

Post by vlasky » Sat, May 30, 2026, 2:48 AM UTC

vunderba wrote: post #58

Nice job. Somewhat related, but one "AI smell" (if you can call it that) is LLMs' desire to add layers of redundant safeguards with things like null coalescing operators and defensive fallbacks so that there’s always some default value. LLMs often seem to struggle with the distinction between happy/unhappy paths and often end up treating everything as optional and "safe". I’m a much bigger fan of surfacing problems l…

Post by touristtam » Sat, May 30, 2026, 6:50 PM UTC

Post by Heavykenny » Sun, May 31, 2026, 11:21 AM UTC

rkuska wrote: post #62

I've tried it on my repository; for go if function is in format `func(...) (T, bool)` and you use it as `object, _ := func(...)` it reports as `Error return value is being ignored` even though it's clearly not an error being ignored (and ignoring the bool ok is a common pattern in go).

Post by TrustDev » Mon, Jun 01, 2026, 7:35 AM UTC

cityofdelusion wrote: post #50

I’m eager to test this out. I have agent instructions to try to limit the worst of this already, but patterns still sneak through. I have a review agent run after every single edit looking for all of the following if you need more ideas for checks: - DRY principle violations, multiple definitions of the same helpers or utilities. - Changes that deviate from existing patterns and architecture already in the code, espe…