Launching today
AI writes your code at 10× speed. Prelint makes sure it's the right code - it reviews every PR against your ADRs, docs and past decisions, and catches product drift before it ships. On teams using several AI reviewers, ~40% of the issues fixed before merge are caught by Prelint.
Free Options
Launch Team / Built With
Few weeks in with Prelint and it's been a genuinely good experience.
Best part for me is that it notices when a change goes against what the docs already say, which means you deal with it early instead of in a painful review later. Solid tool.
Nice to finally see you on PH, good luck!
Prelint
Thanks, appreciate the support! Do let us know about the features you'd like to see going forward, I try to pay very close attention to how people use the tool.
I've watched AI-generated PRs balloon in volume while nobody's actually re-reading the original design docs. Tying review criteria back to ADRs feels like the missing piece most teams skip.
Prelint
Thanks, Grayson! That's if there are any original design docs at all! We have to prepare for a world where there's a lot of micro product decisions being made in Claude sessions, in conversations and on Slack. Very very little people sit down now and do a top-down design doc that they ask agents to implement. So we're building for a world where we need to catch these decisions where they happen and serve+structure them back.
QA engineer here, been using Prelint for a while. A lot of our PRs are AI-assisted now code compiles, tests pass, looks right, but whether it still matches what the team actually decided used to land entirely on me.
Prelint does that pass before I get there. It catches spec drift early, and the notes it leaves on the PR are genuinely useful input for my testing, I go in knowing which areas need attention instead of reading a diff cold.
Good luck with the launch!
Prelint
Thanks for your support Michał, feel free to reach out whenever there's a feature you feel is missing!
My team's biggest AI-coding headache isn't bugs, it's silent scope creep, code that works but drifts from what we actually decided months ago. Tools like this feel overdue.
I like that this treats ADRs as living context instead of dusty docs nobody rereads. Question: does it flag drift retroactively too, or only on new PRs going forward? That distinction matters a lot for legacy repos.
I tried catching this manually with a "does this match my architecture doc" checklist in code review. It worked until velocity picked up and reviewers started rubber-stamping. Would love to know how it handles reviewer fatigue over time.
Prelint hitting "product drift" specifically is such a sharp framing. Most AI code tools obsess over syntax or bugs, but the thing that actually scares me is the AI quietly building something slightly off from what the product was supposed to be
Prelint
Thanks Yibo!
When I first started writing about product drift in February, I wasn't sure if it wasn't too niche. At the time we were one of the very few companies that had fleets of headless agents doing engineering. Now it seems to be picking up so maybe we got it right 😅
The exciting thing is that we built Prelint for ourselves - we had good technical code review tools but they detected if the code was technically correct, not if it was following our architecture decisions and design patterns. When I launched Prelint originally we were surprised how efficient it was at surfacing these small implicit decisions that coding agents make on your behalf.
Looking forward to hearing your feedback!