← 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 pass

Of the 371 repos on the leaderboard, 255 pass in full (69%), 0 pass in part (0%) and 116 fail (31%).

Why agents need it

A linter turns style into something an agent can check. It runs the tool, reads the errors and fixes them, where it would otherwise copy whatever style the nearest file uses. Aider lints after every edit by default, so a repo with no config gives it nothing to lint against.

How we score it

  • 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.

The methodology has the formula that turns checks into a score.

How to pass

Pick the standard tool for your language, commit its config file, and put the lint command in AGENTS.md. A linter that only runs with default settings leaves no file for this check to find.

Which agents count it most

Pass rate by language

Top-scoring repos that pass

Popular repos that fail it