Linter became a mandatory quality contract in AI development

Developer Willis Allstead replaced ESLint with oxlint in his monorepo and claims that when code is generated by AI agents, a linter in CI becomes a mandatory quality contract, unlike instruction files such as AGENTS.md.

Compiled by Sergey KostenchukPublished 2026-09-21Updated 2026-09-21

2026-09-21 Coding

💻 Linter — a mandatory contract in the era of AI code

Developer Willis Allstead explained in his blog allstead.dev why lint is needed when AI writes code. He replaced ESLint with oxlint in his monorepo: a full run was sped up from ~3 minutes to ~1 second, and the team stopped bypassing checks via git push --no-verify.

🌍 When agents write code, the only enforceable quality contract left is deterministic checks: an agent can ignore the AGENTS.md instruction, but not a linter in CI. Put lint on pre-commit for agents and on pre-push with CI backup for humans.

👤 Don't disable lint, speed it up. Junk code "infects" the repository: agents copy patterns from neighboring files. And keep the linter config where the agent cannot write, otherwise it will quietly weaken the rules.

Source 1: https://allstead.dev/blog/why-lint-when-ai-writes-the-code Source 2: https://news.ycombinator.com/item?id=49782185

Sources