Code linting

A linter's job is to make an entire category of review comment impossible. Every rule you enable should retire a conversation nobody should have again.

The failure mode: a lint config so noisy that people run it with --no-verify, or so lax it catches nothing. Both end with the linter ignored. Aim for a config where every reported problem is worth fixing, because that is what keeps the signal trusted.

1. Find out what already exists

Never add a second linter alongside a working one. Check for config files, CI lint steps, and editor settings before proposing anything.

ls -a | grep -Ei 'lint|format|pre-commit|editorconfig|prettier|ruff|eslint'