We did it! Prelint hit #1 on Product Hunt this week - thank you for every upvote, comment and DM Now let me return the favour:
I honestly didn't imagine a launch where we'd have a customer registering every couple minutes - or that I'd spend part of it exchanging comments with one of the world's most popular YouTubers. Wild week.
I replied to every comment on our launch - solo builders, CTOs, investors all interested in the same problem from different angles. Here is how it started in February:
Prelint exists because of one code change. An agent ignored our event-driven architecture and implemented a feature completely bypassing it. The code was technically correct, passed all tests. And nobody made that decision - it was just quietly baked into our product.
That's product drift. It's almost never one big bad call - it's micro-decisions nobody notices for 6 weeks. A change in permissions, a "simplified" billing edge case, a dependency nobody approved. Usually it's good code, wrong product.
So here's my launch offer - not a discount - it's my time.
If you're rolling out coding agents and agentic workflows at your company right now, comment or e-mail me at wojtek(at)prelint.com. I'll share the exact agentic workflows and tooling we use internally to manage 50 production changes a day as a small team and I'll honestly tell you which parts you can solve in-house before you need a tool like ours. These conversations were the best part of the launch and I want more of them :)
Also - if you want to see what your agents have been deciding on your behalf, connect a repo at prelint.com Code PH100 gets you 100$ in free review credits this month - it's full speed AI, but with lane assist.
product drift is the real silent killer with ai code 👀 how do you keep false positves low?
Thanks Petr! The grounded, high quality decision ledger helps. In reviews themselves, we also have grounding mechanisms that anchor comments to very specific ADRs / decisions.
Also - it's interactive and gets better over time. If you add a comment to a pull request that is a false positive, we consider this a part of the decision process and store it for future reference. So even IF a false positive happens, this class of problems happens once and never again.
How does it work?
Good question!
Step 1: It's plug and play - connect your GitHub repo, it understands your code, docs, change history and starts building an ontology of your business. From the start we see it being very helpful at surfacing implicit decisions your agents make (like: small changes to business logic that have an impact downstream) or violating desing patterns your team decided on. For example, you don't have to tell it you're HIPAA or SOC compliant, it's smart at understanding your team's ruleset.
Step 2: As your agents and team work with Prelint, with every interaction it absorbs microdecisions and "product breadcrumbs". It understands if a given decision is made by a human or AI and the authority of the decision maker, understands how the decision collides or supercedes others and allows agents to access this data through CLI.
Step 3: In the future, we see interfaces for non-technical people as extremely important - very often your product, business, sales teams are affected by these microdecisions and they don't event have access to GitHub or ways to course-correct. In 3 months we want to have interfaces for eg your product team or CEO where they can record soundbites that complement or expand the tracked decisions, too.
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!
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!
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.
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.
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
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!
I've been using Prelint for a few weeks now, and it's been a great experience so far. Solid tool, cool to see you finally on PH. Good luck with the launch!
Thanks Daniel, do let us know if there are features you'd like to see next!