Linting
also: linter, linters, lint
Using a tool that automatically scans your code for common mistakes and messy style, without running the app. The tool is called a linter.
Automated checking of source code against rules for style, likely bugs, and bad practices, such as unused variables or suspicious comparisons. Tools like ESLint and Ruff run in editors and CI, and can often auto-fix simple issues.
A spelling and grammar checker for code. It won't judge whether your essay's argument is good, but it catches typos and sloppy sentences before anyone reads it.
Linters catch small mistakes in agent-written code for free. When your agent mentions lint errors, it's usually quick cleanup, but some lint rules flag real bugs worth reading.
Lint found 3 issues: two unused imports, and one piece of screen code that won't re-run when a value it uses changes. That can show stale data, so I'll fix it properly.
Run the linter and fix the errors. Don't disable any lint rules or add ignore comments without asking me first.
Thinking lint warnings are only about looks. Many are about style, but some catch real bugs, like a value that never gets updated.