Lintwell

About

Lintwell reads a single config and drives ESLint, Ruff, clippy and gofmt with consistent severity levels, so a warning means the same thing in every package.

Where Lintwell fits

Lintwell sits in the code editors corner of most stacks, and is aimed at teams who have outgrown doing this part by hand. It runs on CLI and VS Code, and is free to use.

The source is public, so the parts you depend on can be read, forked and audited rather than taken on trust.

What you get on day one

Single source of truth for severities, and per-package overrides that stay readable, editor integration with no extra setup, fails ci with one combined report. The setup is deliberately small: the maker's argument is that a tool you have to schedule a migration for is a tool you will not adopt.

Whether that holds for your team depends on what you already run. The listing below and the feedback from other makers are the fastest way to find out.

What it does

• Single source of truth for severities
• Per-package overrides that stay readable
• Editor integration with no extra setup
• Fails CI with one combined report

• Mara Ellis @maraellis · 2d

  Been using this on a 40-table schema all week. The rollback generation alone saved me twice. One request: a dry-run flag that prints the SQL without touching anything.

• Devin Roy @droy · 3d

  The plain-language summaries are the killer feature. My non-technical PM can review migrations now, which I did not expect to ever type.

• Sana Qureshi @sanaq · 4d

  Works well with Postgres. MySQL support felt a bit behind, the enum diffing missed a case for me. Filed an issue and got a response the same day.