Your linter checks syntax. ReasonLint checks the thinking.

It's an AI code reviewer that runs in your terminal. Point it at a file, a directory, or your staged changes, and it reads the code the way a senior engineer would: looking for hidden assumptions, missing failure modes, edge cases nobody handled, and design choices that will hurt later. Every finding comes with the reasoning, so you know why it matters and what to change, not just that something was flagged.

Add it as a pre-commit hook and it reviews what you're about to commit, automatically. It's a single Go binary: nothing to host, no service to keep alive. You bring your own OpenRouter API key; the tool has no backend of its own.What it is notIt's not a PR bot and it doesn't replace your linter. Linters are fast and deterministic and you should keep them. ReasonLint is for the moment after the linter passes: before you push, when you've just finished a long AI-assisted coding session, or when you're reading unfamiliar code and want someone to explain why it's fragile.

I'd love your feedback ✨✨

Tell me about a bug your linter missed. Paste the snippet in the comments and I'll run ReasonLint on it and share what it finds, including the misses. That's the most useful thing you can do for this launch.