Editorial photograph evoking static analysis of AI-generated code — magnifying glass over printed source.
    Work / 05 · Slopgate

    A linter for the patterns AI leaves behind.

    Slopgate targets the tells that Copilot, Claude Code, and Cursor leave in a codebase — patterns generic linters miss because they don't know what AI-written code looks like.

    Role

    AI-code quality guardrail

    Year

    2026

    Surface

    CLI · CI integration

    Status

    Open source

    01The problem

    The new bugs do not look like the old bugs.

    Most linters were written for code humans typed character-by-character. AI-generated code fails differently: plausible imports that don't exist, duplicated helpers across files, error handling that swallows the cause, comments that re-describe instead of explain.

    Slopgate catalogs those patterns and flags them at the boundary, before they reach review.

    Darkroom red. The drafts pile up. The good one survives.

    Darkroom red. The drafts pile up. The good one survives.

    02The approach

    Boring guardrails for an interesting new kind of mess.

    Slopgate is a CLI you can install in seconds. It runs locally, in CI, or as a pre-commit hook. Rules are tuned for the actual artifacts the models leave — not for an abstract notion of "AI slop".

    Open source on purpose. The whole point is that the rules are visible and challengeable.

    Specifications

    Form factorSingle-binary CLI · pre-commit · CI step
    LanguagesTypeScript · Python · expanding
    RulesHallucinated imports · duplicated helpers · swallowed errors · narrating comments
    LicenseOpen source — MIT

    You can have AI write the code. You should not let it ship it unchecked.

    Studio note

    Previous work

    SkillSwap

    Next work

    VeriLink