EN
Back to the archive

The archive · Developer & Business Tools · Product decision · 2026

Prelint bets AI code needs a decision ledger: PH #1 with 548 votes, $1 per review

Prelint reviews every pull request against ADRs and past decisions to stop AI 'product drift'; PH #1 on 2026-07-29, $1 per review.

Prelint

The betTeams shipping AI-written code will pay for a decision ledger that checks every pull request against specs and past decisions, catching product drift the day it appears.Live

What the business is

Prelint is a decision-ledger product-review tool: teams connect GitHub or GitLab, and every pull request gets a roughly 20-second decision review that flags changes contradicting earlier choices — billing logic, compliance, dependencies, domain language, scope — then records the decision with who made it, when, and whether an AI or a human decided. Pricing is $1 per completed review with prepaid credits; open-source projects are free.

How it started

The founding moment came when an AI agent ignored the team's event-driven architecture and built a feature by bypassing it: the code worked and passed review, but was not what the team wanted — 'product drift'. Wojtek Szkutnik, previously co-founder and investor at Kalamba Games (2017–2024), and CTO Krzysztof Kulig built Prelint to record and check product decisions; per prelint.com the company began in AI for smart buildings before landing on the decision ledger, and growth lead Irena Pawlowski joined in March 2026.

What happened

The 2026-07-29 Product Hunt launch (#1 Product of the Day, 548 upvotes) introduced the ledger model: every pull request gets a short decision review, approved decisions become context agents use on the next task, and contradicting decisions lower confidence so agents ask before building. Company-published research reviewed 56,706 pull requests across 331 open-source repositories, flagging 36.6% of changes when documentation existed versus 13.3% without, and Prelint says teams already running several AI reviewers see about 40% of pre-merge fixes come from its checks.

How it ended up

As of September 2026 Prelint is live at $1 per completed review with $10 free credits, SOC 2 Type 1, per-tenant review sandboxes that are destroyed afterward, US hosting and self-hosted options, and prelint.com reports 40% of code changes on Linux Foundation projects now quote its reviews.

Background

Prelint is a product-review tool built around a 'decision ledger'. Where CodeRabbit, Greptile and BugBot check whether a pull request is technically correct, Prelint checks whether the change matches the product the team decided to build: specs and architecture decision records live in the repository, every pull request is compared against them in about 20 seconds, and each approved decision is recorded with who made it, when, and whether a person or an AI decided it.

The founding problem was product drift. The team watched an AI agent ignore their event-driven architecture and implement a feature by bypassing it — the code worked, passed CI and review, but was not what they wanted. Wojtek Szkutnik, previously co-founder and investor at Kalamba Games, and Krzysztof Kulig built Prelint to keep those decisions visible; prelint.com says the company started in AI for smart buildings before landing on the ledger product.

Prelint launched #1 Product of the Day on Product Hunt on 2026-07-29 with 548 upvotes. Its model is usage-based: one dollar per completed review, prepaid credits, free for open source, with SOC 2 Type 1 and review sandboxes destroyed after each run. Company research across 56,706 pull requests in 331 open-source repositories found 36.6% of changes flagged when docs existed versus 13.3% without, and it says roughly 40% of issues fixed before merge on multi-reviewer teams come from its checks.

The bet is that as coding agents write more production code, review shifts from 'does it run' to 'was this decided': agents ask the ledger before writing, auditors get a dated record of who decided what, and product owners see an unreviewed six-week-old decision while the fix is still one edit. Prelint positions itself as complementary to technical reviewers, with only about 4% finding overlap.

What has to be true

  • AI agents ship technically sound code that ignores architecture and business rules; no test fails, so only an intent check catches it.
  • Recording each decision with a source and date turns reviews into an audit trail and into context the team's own agents reuse.
  • Pricing per completed review with no seats or subscriptions matches how agents actually generate pull requests.
  • Being a complementary layer rather than a CodeRabbit replacement avoids the crowded 'find the bug' market.

What can be applied

Review intent, not just correctness: when agents write code faster than humans can read it, the constraint is whether changes match decisions, and recording each decision makes drift traceable.

Aftermath

As of 2026-09-06 Prelint is live and usage-priced: $1 per completed review with prepaid credits, free for open source, SOC 2 Type 1, US hosting with zero data retention at the model provider, and optional self-hosted deployment. Its site reports 40% of code changes on Linux Foundation projects now quote a Prelint review. Open questions are whether teams keep documentation sharp enough for the ledger to stay accurate, whether agent-era review becomes a default inside GitHub rather than a paid add-on, and how far the tool moves from the pull-request gate to ticket-stage checks.

Sources

spotted an error? The archive wants to know.

Your turn

You just read one. Describe what you are building, and see who is betting on the same thing.

Free account · 3 free questions · no card

Related cases