A fresh new take on pull-request iteration for the era of AI-generated code.
Pull-request workflows haven't evolved to match how code is written today. Developers use AI-assisted coding more often than not, and the DevOps market keeps pouring resources into code generation efficiency. However, code review tools haven't seen a significant change in 20 years. The human reviewer is still the one accountable, now for a larger volume of code they didn't write themselves. There is a high cost to this. Developers are frustrated, code quality suffers, and pull requests sit waiting while the work built on top of them can't move forward.
We started from our own lived problem as developers working in teams, and then decided to validate it. We followed discussions on public developer forums, published articles that provoke reactions and pull feedback, and finally started direct conversations with real users. Each stage was validated enough to justify the next.
"What I really want when I'm reading source code is to hover over a line and ask 'why was this done this way?' That reasoning almost never makes it into the docs but it's exactly what lives in the review discussion."
Our review flow is built around three decisions that remove the waiting and the back-and-forth discussions that slow down the process:
"In every review tool I've used, I never know what order to review files in. As the author, I just want to float the important files to the top so reviewers look there first."
I worked on the research, visual design and frontend implementation of Lubeno. Because I build what I design, the interface arrived grounded in what the hybrid Git/Jujutsu architecture could actually support, and design decisions fed directly back into how we shaped the product.
Organizations that host and collaborate on Git can adopt Lubeno gradually since there's no migration cliff. A free version serves individual developers and small teams, and a comprehensive paid subscription serves larger companies.