Prelint

Super interesting. I'm one person shipping with Claude Code daily. I had wrongly assumed drift was a coordination problem: several people, nobody reading each other's decisions. But what i found is that my own documented decisions go stale against my own code, and then they propagate.Two from this month. A task in my tracker carried an explicit "do not do X without first verifying Y" warning. I wrote the checklist for that exact task without reading its notes, and caught it only when I went to close the task afterward. Separately, my canonical brand doc described a logo treatment that the actual shipped asset files contradicted. The doc was wrong for weeks and seeded the wrong version into an outgoing email template before I noticed.Neither was an agent going rogue. Both were correct-looking work built on a confidently stated stale premise.So my question: your supersession detection sounds aimed at documents contradicting each other. Does it handle a document contradicting the artifact it describes? The rotten context that actually cost me was doc versus reality, not doc versus doc, and the docs were the ones asserting loudest.

AI-generated code will only become more common, so governance tools like Prelint are going to be must-have!

Congrats on shipping. Whats the roadmap looking like?

Congrats Wojtek. Did you build this out of your own frustration or what inspired to think of solving this problem?

Are you primarily targeting product and dev teams?

Congratulations. Does Prelint suggest the closest approved design pattern when it detects a violation?

When you build with AI, product consistency tends to erode gradually. Tools like Prelint can help stop that before it becomes expensive. Congrats on the launch.

the "decision ledger vs check code against docs" framing is what actually clicks for me. i keep a section in my own CLAUDE.md that's a manual, extremely low-tech version of this, not architecture notes, just "already tried this, here's why it didn't work" so the agent doesn't quietly rebuild the same mistake three months later. what i can't do by hand is catch the drift in real time instead of noticing the pattern repeating after the fact.question on an existing repo: does the ledger backfill decisions from git history, or does it only start learning from the point you connect it?

Prelint is interesting because it seems to be focusing on the product intent. A lot of times AI can take its own direction, catching it soon from drifting by a tool is a great idea indeed!!

The tagline makes me wonder about the source of truth Prelint uses to detect product drift in AI-written code. Is it checking against product specs, tickets, existing code patterns, design docs, or something else? That distinction feels important, especially for teams already using AI coding tools but not always keeping requirements perfectly structured.

How does Prelint differentiate between a real product decision issue and a technical choice that only looks risky from the outside?

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?

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...

This is amazing, over the past years we were following coding architecture and patterns religiously and now AI generated code just done their job which is good but diverting from current architecture and design patterns, I think Prelint is the solution for this

Most of the drift I run into is scope. I ask for one thing, the agent fixes three others along the way, and each one looks reasonable in the diff. I ended up writing the boundary into every prompt instead of catching it afterwards. Not sure whether you flag that kind of thing or only decisions that change how the product behaves. The distinction you are drawing is the right one either way. Congrats on the launch!