AISlop, a CLI for catching AI generated code smells

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.

Hacker NewsToolAISource
0Sign in to voteCopy link

FL score

62

out of 100

Verdict

VALIDATE

high confidence

Competition

No competitor data yet

Trend

No signal yet

A linter for AI-generated code that catches anti-patterns humans miss in LLM outputs.

The pain

Developers using Claude, GPT, and other code-generating AI models get syntactically valid code that contains hidden problems: empty catch blocks, dead code, duplicated helpers, and useless comments. These pass tests but degrade code quality over time. Manual review is tedious and inconsistent.

The gap

Existing linters (ESLint, Pylint) catch syntax and style. They don't catch the specific patterns that AI models repeatedly generate, the structural shortcuts and lazy patterns that work but shouldn't ship. No tool currently bridges this gap.

Build angle

Start with a focused CLI that integrates into git hooks and IDE workflows. Build detection rules for the top 10-15 AI-specific code smells (empty error handlers, redundant comments, unused variables in AI-generated blocks). Validate with developers actively using AI pair programming. Expand to multiple languages only after proving the core value in one.

Strengths

  • Solves a real, immediate problem for a growing user base (AI code generation is mainstream now)
  • Local-first approach removes privacy concerns that block adoption
  • Integrates into existing workflows via hooks rather than requiring behavior change
  • Founder has direct experience with the pain point
  • Low barrier to try (npx command, no setup)

Risks

  • Market timing unclear, AI code generation adoption varies widely by team; early adopters may be small
  • Rule detection could be brittle; AI patterns evolve faster than rules can be written
  • Monetization path undefined; hard to charge for a CLI tool developers use once per project
  • Competitive risk from IDE vendors (GitHub Copilot, JetBrains) adding this natively
  • Requires ongoing maintenance as AI models change their output patterns
  • No evidence of product-market fit yet; single founder, early stage

Questions about this idea?

FlyBot reads the scoring and gives you a second opinion on “AISlop, a CLI for catching AI generated code smells”.

Open FlyBot