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.
AI agents ship code that passes every test - and quietly makes product decisions that break your product. @Prelint is the decision layer for AI-written software.
Tools like CodeRabbit check if your code is correct; Prelint checks if it does the right thing.
Live on Product Hunt today: worth a look and vote: https://www.producthunt.com/prod...
Battery AutopilotPut your MacBook battery on AI autopilot
Promoted
the thing I'd worry about is ADR rot. checking a PR against decisions that are themselves six months stale just enforces the wrong thing, confidently. does it ever flag the ADR as the problem rather than the code...
Good point, Alex. Not only I agree with this, we're also building the product that actually helps with it.
We address this in a couple ways: proactively, whenever changes are introduced or mentioned, our system understands the authority of the claim being made and either supersedes the previous decisions, or flags it to the humans and AIs - it happens in three surfaces - PRs that touch the docs or code, CLI where the agents can actually see not only the ADR but also the "product breadcrumbs" that led to this decision. So if there's multiple "decisions" touching an ADR, we will squash and decay the irrelevant ones and provide a "when and why" for ones that make contradicting claims.
Report
Setup was painless and it actually flagged a comment in our PR that contradicted a decision from a doc two months back, which surprised me. Curious how it holds up on bigger repos.
Thanks for your vote of confidence, Malika! With bigger repos, it actually works even better because it has more context on historical decisions and design patterns.
Report
We were using similar thing in my project but built in-house, that's actually super valuable
Yes! I had someone ask why is it not a Claude Code skill last week, and the honest answer is - it is, for the first 10% of the job it works super well.
I love that companies now build parts of the tooling in-house, we actually advise some enterprise partners on it too. I think it's validation not competition 😊 I cheer for everyone struggling with the same problem and when it escalates we're always there to provide a best-in-class solution based on all of our experience.
Also - if your company is still looking at these kinds of processes - feel free to message or DM me, I'll happily advise on in-house processes too and share our agentic workflows and if Prelint can be of help at any future time - even better.
Report
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.
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.
Report
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.
Thanks for your support Michał, feel free to reach out whenever there's a feature you feel is missing!
Report
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.
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.
Report
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.
Thanks William! Yes. Also, the problem is often that AIs try to add something that genuinely adds value - a feature, design pattern but it just gets baked into the code without a human ever knowing about it - and it creates a spaghetti of the right thing built at the wrong time.
Do try Prelint for your projects and let me know what your team thinks :)
the thing I'd worry about is ADR rot. checking a PR against decisions that are themselves six months stale just enforces the wrong thing, confidently. does it ever flag the ADR as the problem rather than the code...
Prelint
Good point, Alex. Not only I agree with this, we're also building the product that actually helps with it.
We address this in a couple ways: proactively, whenever changes are introduced or mentioned, our system understands the authority of the claim being made and either supersedes the previous decisions, or flags it to the humans and AIs - it happens in three surfaces - PRs that touch the docs or code, CLI where the agents can actually see not only the ADR but also the "product breadcrumbs" that led to this decision. So if there's multiple "decisions" touching an ADR, we will squash and decay the irrelevant ones and provide a "when and why" for ones that make contradicting claims.
Setup was painless and it actually flagged a comment in our PR that contradicted a decision from a doc two months back, which surprised me. Curious how it holds up on bigger repos.
Prelint
Thanks for your vote of confidence, Malika! With bigger repos, it actually works even better because it has more context on historical decisions and design patterns.
We were using similar thing in my project but built in-house, that's actually super valuable
Prelint
Yes! I had someone ask why is it not a Claude Code skill last week, and the honest answer is - it is, for the first 10% of the job it works super well.
I love that companies now build parts of the tooling in-house, we actually advise some enterprise partners on it too. I think it's validation not competition 😊 I cheer for everyone struggling with the same problem and when it escalates we're always there to provide a best-in-class solution based on all of our experience.
Also - if your company is still looking at these kinds of processes - feel free to message or DM me, I'll happily advise on in-house processes too and share our agentic workflows and if Prelint can be of help at any future time - even better.
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.
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!
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.
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.
Prelint
Thanks William! Yes. Also, the problem is often that AIs try to add something that genuinely adds value - a feature, design pattern but it just gets baked into the code without a human ever knowing about it - and it creates a spaghetti of the right thing built at the wrong time.
Do try Prelint for your projects and let me know what your team thinks :)
DMs always open if you ever need support