Anti-AI-Slop Linting

What is it

Anti-AI-Slop Linting refers to a nascent category of developer tooling that uses rule sets—such as those built into Oxlint—to flag and reject TypeScript patterns considered “AI-flavored” or low-evidence. These rules aim to catch code that looks plausible but lacks strong logical grounding, which is a common artifact of AI-generated suggestions. As a linting approach, it sits squarely in DevTools, first appearing on GitHub on 2026-09-06, though it currently holds a nascent stage score of 41/100.

Why now

The term has only 1 mention across GitHub sources, indicating it is just entering developer discourse rather than being widely adopted. This timing suggests early experimentation by tooling maintainers who are reacting to the growing volume of AI-assisted code in repositories. The low mention count means the concept is still undefined and unstandardized—making it a prime moment for indie tool builders to shape the rules before larger players formalize them.

Who should care

Indie developers who rely heavily on AI code assistants should track this to avoid shipping code that fails linting in stricter CI pipelines. SaaS founders building DevTools or code-review products should watch this space, as a nascent category with 41/100 score implies room for a dedicated linter or plugin that could become a must-have. Product managers for developer experience teams should also monitor it, since anti-slop rules could influence how AI-generated code is reviewed and trusted in production environments.