ai-deslop plugin catches AI's sloppy TypeScript

ai-deslop, a plugin posted to Show HN on October 14, 2026, still lacks a Japanese explanation. The test setup was fully local: no LLM API key or cloud account was needed. The deliberate sample combined common AI-writing habits in one place — a double cast from unknown to a domain type, a filter().map() chain, a conditional spread, and a test that only asserted a mock had been called. Running oxlint on that code produced 25 errors across 16 rules at exit code 1. The author then refactored toward a single I/O-boundary parse function and domain types, and the same lint run returned 0 warnings and 0 errors in 304ms on 1 file with 135 rules.

Beyond the happy path, gotchas the README does not cover are documented. Installing ai-deslop without oxlint-tsgolint halts the run; using a TypeScript config file on Node 20.20.2 fails even though the error message mentions ^20.19.0; and when environment variables like CLAUDECODE or AI_AGENT are set, oxlint silently switches to one-line agent output. The author also notes the plugin is opinionated — no-shape-in-symbol-names bans names like UserShape outright, and no-module-mocking bans vi.mock — and that these can be turned off per team policy. For gradual adoption, the post suggests running rules as warnings under a --max-warnings ceiling and lowering the ceiling as fixes land, with the ceiling matched to the current warning count.