Nicheloom visits: 58,345 all-time · 7,637 in the last 7 days

The opportunity tracker for new startups.

Today: 1,008 launches · Niche of the day: specialized calculation tools · See what launched today →

AISlop, a CLI for catching AI generated code smells

Get picks like this daily. Today's launch numbers, the top launches, AI and tech news, and a daily opportunity pick, straight to your inbox.

Want to reach these readers? Sponsor an issue.

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.

HN · launched May 29, 2026 · 73 upvotes (top 13%) · 0 views

Niche: automated code review tools · 204 launches, 7 in the last 7 days ▼ -22% · Explore this niche →

Category and tags

  • Horizontal
  • Dev tools
  • Developer
  • Not AI
  • Hobby / open-source project

Visit website ↗ Source listing ↗

Could you build this?

Yes It is a CLI linter that parses ASTs using libraries like tree-sitter to detect common code smells such as empty catch blocks or duplicated helpers.

Discussion

20 comments analyzed.

Competitors mentioned: Other language-specific linters (half a dozen used in rotation), Deterministic linters

Concerns raised: False positives on language-specific patterns (Go's ok-ignore idiom), Difficulty distinguishing junior dev mistakes from AI-generated code, Scoring/calculation appears incorrect (Postgres showing 56/100 failing with only 6 warnings), Over-detection of redundant safeguards may discourage legitimate defensive programming, Chicken-and-egg problem: definition of 'slop' varies by model training/RLHF

Feature requests: Allow-list syntax to mark intentional patterns (like Rust's #[allow(...)]), Dead code detection, Detection of redundant defensive code and over-use of null coalescing, DRY principle violations and architectural pattern deviations, Unnecessary guard code and overly backwards-compatible changes

Competitors

Other products that read as similar to this one : 296 launches clear the similarity bar, closest 8 shown.

Attention rank: #42 of 297 (itself plus its competitors, highest first, normalized so YC and Product Hunt are compared fairly).

Launched 200 days after the earliest competitor.

The niche, labels, vibe code rating and competitor comparison on this page are analysis by Nicheloom. If you use them, please credit nicheloom.com. How you may use our data.