Show HN: AISlop, a CLI for catching AI generated code smells
21–30 of 70 posts
Re: Show HN: AISlop, a CLI for catching AI generated code smells
#22Re: Show HN: AISlop, a CLI for catching AI generated code smells
#23Re: Show HN: AISlop, a CLI for catching AI generated code smells
#24> 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.
Re: Show HN: AISlop, a CLI for catching AI generated code smells
#25Re: Show HN: AISlop, a CLI for catching AI generated code smells
#26Re: Show HN: AISlop, a CLI for catching AI generated code smells
#27Re: Show HN: AISlop, a CLI for catching AI generated code smells
#28Re: Show HN: AISlop, a CLI for catching AI generated code smells
#29One funny thing I see it doing is deleting seemingly random comments lines, for example if a file has a comment that spans multiple lines but doesn’t use a multi line comment syntax. It just chooses one at random transforming the once useful comment into slop.
Re: Show HN: AISlop, a CLI for catching AI generated code smells
#30I 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 {…