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.
Nas.com
Are you primarily targeting product and dev teams?
Prelint
@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?
Prelint
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
ConnectMachine
Congrats on shipping. Whats the roadmap looking like?
Prelint
@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
Macaly
product drift is the real silent killer with ai code 👀 how do you keep false positves low?
Prelint
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?
Prelint
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!
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!