The review process your team has never had.
Where Changes get context, feedback gets meaning, and code ships faster.
Introducing Craft
I've watched engineering teams lose weeks every year to a problem nobody talks about: code review has no process.
Not because developers are careless. Not because teams don't care about quality. But because nobody has ever built a real product for the review workflow. GitHub gives you a diff viewer and a comment box. That's not a process — that's a file viewer with a thread attached.
The result is familiar to anyone who's shipped software. PRs that sit for two days because nobody knows who's responsible. Reviewers who leave forty comments with no indication of what's actually blocking the merge. Authors who read "looks mostly good but a few things" and have no idea what to fix first. Engineering leads who ask "why is velocity down?" and get shrugged shoulders.
Teams aren't bad at code review. They've just never had a product that takes it seriously.
Craft is that product. It's not a better diff viewer. It's not an AI that summarizes your PR. It's the workflow layer that has always been missing — structured context on every change, feedback that means something, verdicts that tell everyone exactly what happens next.
We're building this for the engineering lead who is tired of review being a black box. For the senior engineer who cares about how their team works, not just what they ship. For the team that wants to get better at the most important part of software development — the moment before code ships.
We're just getting started. If this resonates, we'd love to hear from you.