Linting

Sub-techniques

• Correctness rules V1005.001

  Rules for likely bugs: unused results, shadowing, unreachable code, wrong comparisons.

• Convention rules V1005.002

  Project conventions encoded as lint rules instead of review comments.

• Custom lint rules V1005.003

  Repository-specific rules written as plugins or pattern rules for mistakes that recur in review.

How to build it

1. Enable the linter's recommended set and fix or baseline existing findings.
2. Turn recurring review comments into custom rules (an ESLint plugin, a Semgrep rule, a Clippy lint config).
3. Fail CI on new findings only, so the baseline shrinks without blocking work.

Signals in a repository

• Lint config in pyproject.toml ([tool.ruff]), eslint.config.js, .golangci.yml or clippy.toml.
• A CI job named lint, or a lint script in package.json, Makefile or justfile.
• Inline suppressions (noqa, eslint-disable) show which rules are enforced.