Verification · Static analysis · Linting
Convention rules
Project conventions encoded as lint rules instead of review comments.
How to build it
- List each project convention that reviewers repeat, such as import order or naming.
- Enable the built-in rule for each convention where one exists, and write a custom rule where none does.
- Pin the linter version so rule changes do not surprise contributors.
Signals in a repository
- Rule selections for naming or import order, such as ruff's N or I rule sets.
- A .golangci.yml linters list that enables revive or stylecheck.
In practice
175 repositories run a tool for this check in the scanned set.
ruff-check· 64 reposeslint· 107 reposgolangci-lint· 26 reposclippy· 45 repos
Examples
-
freeCodeCamp/freeCodeCamp ·
eslinteslint --max-warnings 0 -
nousresearch/hermes-agent ·
ruff-checkruff check --output-format json --exit-zero > $R/head/ruff.json -
TheAlgorithms/Python ·
ruff-checkruff check --output-format=github . -
microsoft/vscode ·
clippycargo clippy ${args[@]} -- -D warnings -
ollama/ollama ·
golangci-lintuses golangci/golangci-lint-action