With the introduction of AI into our workflow, we started using it in many different ways, and we took different paths in how we use it for sowftware engineering.Stage, treated AI as a tool to chapter a PR into different sections to make reviewing a large PR easier by chunking it into chapters with AI generated summaries, they realized that code review is the bottleneck now, but their take on how AI can improve or speed up a PR review is incorrect from my perspective.Adding more AI generated stuff to an already large AI-generated code just makes the review slower and more daunting. but their product inspired me to do it the right way.Meet Pyor! (pyor.review) Pyor s goal is to use AI to reduce the amount of code required to review, not increase it.Unlike GitHub, Pyor lists code changes in a chronological order for faster and easier review that s linear to avoid context switching, it also uses AI to group the mechanical noise in a PR so a reviewer skims it and spends real attention only on the changes that matter.we built Pyor by engineers to help engineers move faster in the AI era, and that s our bet.