Use a faster native linter without losing rules

Move supported lint checks to a fast native implementation and preserve coverage for rules it does not support.

Prompt

Evaluate and apply this CI technique to my repository: Use a faster native linter without losing rules.

Move supported lint checks to a fast native implementation and preserve coverage for rules it does not support.

Read the technique and its source-backed company examples: https://starsling.dev/ci-playbooks/techniques/native-lint-tools.md

Inspect this repository’s CI workflows, build and test commands, dependencies, and recent run timings. Identify where this technique applies and explain the expected benefit using this repository’s evidence.
Measure a baseline from recent comparable runs: elapsed time, queue time, runner minutes and failures where available. If data is unavailable, say what cannot be measured.
Compare relevant company approaches, checking prerequisites, platform differences and tradeoffs. Rank applicable options by evidence, fit and measurable opportunity; do not present company results as predictions for this repo.
Recommend the smallest safe change, show what checks and fallback paths remain, and ASK ME WHICH CHANGE TO APPROVE BEFORE EDITING ANY FILES.
Only after approval, work on a new feature branch, make one reversible change, and open a reviewable pull request. Never merge or push to a default or protected branch.
Keep required checks, test coverage, deployment and release behavior intact. Validate the change and compare equivalent runs where possible; report limitations and what should be monitored after merge.

View all playbooks

How companies used this technique

Read what each company changed and follow the original sources.

Run native lint without losing unsupported rules

After removing its type-information dependency, Linear moved lint work to Oxlint. Syntax-only rules are straightforward to port, and Oxlint reduced the CI runner-minutes spent on linting.

Use it when: A qualifying ESLint step remains on the slowest path after addressing type-aware overhead.
Before applying it: Retain ESLint for unsupported plugins and rules; benchmark equivalent file and rule coverage.

Lint with one fast native tool

This is a community contribution to Spotify's luigi project. Luigi's lint ran flake8 and isort, two separately configured tools. The change adds a ruff configuration to pyproject.toml, replaces the flake8 tox environment with a lint environment, points the GitHub Actions matrix at it, and applies ruff's fixes and formatting across the codebase.

Use it when: A lint or format step runs several Python tools that ruff replaces.
Before applying it: The first run rewrites files to the new rules and formatting, so land those automated fixes in commits separate from the configuration change.

How companies used this technique

Run native lint without losing unsupported rules

Lint with one fast native tool

Related techniques

Accelerate required type checking with a native compiler

Keep the lint rule, remove its type-graph dependency

Company Playbooks