No CLI enforcer for AI-generated code smells that runs in CI without an LLM at runtime
AI coding agents leave characteristic patterns in codebases: empty catch blocks, narrative comments, dead helper functions, duplicated code, and unsafe type casts. These patterns pass tests but accumulate as technical debt. A March 2026 arxiv study analysed 1154 posts across 15 Reddit and HN threads and found three clusters of developer pain: review friction, quality degradation, and systemic forces. AISlop CLI launched March 2026 and reached 294 GitHub stars with 73 HN points in its first Show HN, proving real demand for a deterministic local scanner that catches AI-generated code smells without LLM at runtime, so teams can gate it in CI.
A CLI tool that flags AI-generated code patterns in CI without running an LLM at runtime
522 โฒScore Breakdown
Social Proof 3 sources
Existing Solutions 2 competitors
Gap Assessment
AISlop (294 stars, March 2026) is the only tool focused on AI-specific patterns; SonarQube covers general smells but has no AI-pattern ruleset and requires cloud/server; market is early.