← all checks

Linter and formatter config: instant feedback for AI coding agents

This check looks for a committed linter or formatter config: ESLint, Prettier, Biome, Ruff, rustfmt, Clippy, golangci-lint, RuboCop, clang-format and about twenty others.

How many repos commit a linter or formatter config?

Of the 401 repos on the leaderboard, 262 pass in full (65%), 0 pass in part (0%) and 139 fail (35%).

Why do AI coding agents need a linter config?

A linter makes style checkable. The agent runs it, reads the errors and fixes them, instead of copying whatever the nearest file does. Aider lints after every edit by default, so without a config it has nothing to lint against.

What counts as a linter or formatter config?

  • Full pass: a config file for a supported tool, or a [tool.ruff], [tool.black], [tool.flake8], [tool.pylint] or [tool.mypy] section in pyproject.toml.
  • Fail: no config found. We do not run the linter.

How checks become a score: methodology.

How do I add a linter config to my repo?

Commit the config for your language's standard tool and put the lint command in AGENTS.md. A linter run on default settings leaves no file to find.

Which AI coding agents weigh a linter config most?

Pass rate by language

Top-scoring repos that pass

Popular repos that fail it

Every check, grouped into what to do first: how to make your repo ready for AI coding agents.