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.
Congratulations. Does Prelint suggest the closest approved design pattern when it detects a violation?
Thanks for the question Kumar! It doesn't suggest a specific line-by-line code solution (we think your agents are pretty good at that) but it does quote a specific ADR or decision that typically includes the right way to do it in case of design patterns.
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.
Congrats on the launch guys! What kind of integrations do you guys have?
Thanks Paulina! We add more integrations every week. You can assume we integrate with all major product management tools like the Atlassian suite, Notion, GitHub Issues, Linear as well as meeting recorders like Read.ai etc. We have a lot of expansion work going towards Slack as well (here the biggest problem is noise so we're working on eg attaching Slack threads to specific decisions).
The biggest limitation is that for now we plan to stay GitHub-native for source control until someone gives us a good reason to expand.
Congratulations on your launch! quick minute question: couldn't someone give instructions to the AI coding agent to check specification document or product design document before shipping code?
Thanks, Richard! They could and should and it does a great job at detecting the first 20% issues.
Our core strength is that in the background of a simple "reviewer" we store a decision ledger that understands not only "what is written in the docs" (this you can compare using a Claude skill) but helps companies organize colliding specifications and decisions, understand how they supercede and override each other and which require human attention. We also understand the authority of the person making the decision (and whether it's a human or an AI).
As a starting point we are quite good at squashing and deduplicating decisions out of the box to address messy documentation, but we also have CLI tools that allow users to iterate on the ground truth that Prelint stores, understand which docs clearly contradict each other and just need addressing.
The problem is also that most teams now create design docs on the fly - so the issue is often not "does the code follow the docs?" but "does anyone know what the AI is actually building?" - and this is a problem that both small and big teams have. In larger orgs it's often a bigger mess because there's less transparency and product and business people get completely lost.
@wojtekszkutnik Thanks for the quick response. I completely agree that because AI can do it faster and easier most teams don't sit and take time to plan the design and requirements carefully. AI is a tool and will do what it thinks you want to accomplish. So I totally get it now. Well done solving an emerging problem for coding.
Are you primarily targeting product and dev teams?
@nuseir_yassin1 oh hey Nas! Right now these are the parts of the companies that already understand the problem we're solving (although typically the conversation actually starts with CEO/C-levels who want AI but with lane assist) - dev teams want to be more efficient and product teams want to understand what the hell IT has been building.
This and for agents - we make a lot of design decisions by mocking tools eg our CLI and looking how agents try to use them - what commands they try to call, what filters to apply etc. So we're kind of trying to create tools that agents like to use.
Long term, we get a lot of requests from all over - today I had people mentioning exec teams, sales teams, support teams that need to occasionally understand and act on product nuances.
Congrats Wojtek. Did you build this out of your own frustration or what inspired to think of solving this problem?
Hey Raghav! It was an agent that ignored our event-driven architecture and implemented a feature completely bypassing it. Then we started exploring and realised how big a gap we were facing - we just prototyped it and people started quickly putting a lot of trust in Prelint seeing the results
Congrats on shipping. Whats the roadmap looking like?
@syed_shayanur_rahman
8h of sleep after I'm done with the launch.
SOC2 finalised in the next days
Lots of work on CLI/MCP
Integrations, integrations
Significant visual overhaul of our Brain interface
Mobile apps with dedicated voice interfaces for non-technical people to add sound bites clarifying specific decisions and just ramble about product
Optimisations so that we can offer more kinds of re-reviews at better prices