Build an AI code review bot in 30 minutes with Vercel Eve

**Claire Vo** (0:00)
Everybody is drowning in AI created PRs. When anyone can code, anyone can cook, and anyone can vibe anything to GitHub, that means that a lot of us are sitting on a big queue of pull requests that then we have to review. If you are an engineering leader or a software engineer in a company that has embraced AI in any way, shape, or form, you feel this pain and I get this question all the time. We've figured out how to code with AI. Now, what do we do with all these PRs? Well, people smarter than us have figured this out. And you know what the answer is? You don't have to review all your PRs. Yep, you heard it here first. You do not actually have to review one-on-one by a human all those PRs. So in today's episode, I'm going to show you how to build your own PR review, risk scoring, and automatic approval bot. So you can take all the low-risk PRs off your plate, get those to production, and focus on the ones that really require your human expertise. This episode is inspired by a couple folks, especially our past How I AI guest, Brian from Intercom, who has led the way in auto-scoring and auto-approval PRs. But I'm going to show you exactly how it gets done, and we're going to get it done very quickly in this 30-minute How I AI mini episode. Let's get to it. This episode is brought to you by Work OS. AI has already changed how we work. Tools are helping teams write better code, analyze customer data, and even handle support tickets automatically. But there's a catch. These tools only work well when they have deep access to company systems. Your co-pilot needs to see your entire codebase. Your chat bot needs to search across internal docs. And for enterprise buyers, that raises serious security concerns.
That's why these apps face intense IT scrutiny from day one. To pass, they need secure authentication, access controls, audit logs, the whole suite of enterprise features.
Building all that from scratch, it's a massive lift. That's where Work OS comes in.
Work OS gives you drop-in APIs for enterprise features, so your app can become enterprise ready and scale up market faster. Think of it like Stripe for enterprise features.
Open AI, Perplexity and Cursor are already using Work OS to move faster and meet enterprise demands.
Join them and hundreds of other industry leaders at workos.com. Start building today.
Okay, I know what you all are thinking. You're thinking, Claire, you are crazy. Of course, I have to review every PR that comes out of AI. That's just how it's done. We review all of our human PRs, I have to review all of our AI PRs. And I am telling you, in 2026, the answer is you can safely not review PRs by putting AI in the loop. And I want to call attention to two blog posts that have really inspired me in this process. One is from Intercom about how they made AI approved PRs. Safe, if you don't know, Intercom has 2x, 3x their PR throughput. They are shipping a lot of code. That means they had a lot of code to review. And so they built a PR review agent that scores their PRs and then auto approves them. And what I love about what Intercom has done here is they don't just worry about speed and velocity and volume. Yes, they've multiplied the PRs across their R&D organization. Yes, they want to get those PR cycle time down in those reviews out quickly. But what they really think and what they've proven with the co-adoption of AI is that AI approved PRs and AI written code in general, can be even safer and even higher quality than what you're doing with just a human in the loop. And so they have used AI as an advantage when it comes to safety and quality, as opposed to a disadvantage for safety and quality. And to set the vision of what you can expect here, I love that they shared some metrics. One is that AI-approved PRs are approved faster, actually five times faster than their human PRs. So one, you are getting some speed. Two, they are seeing higher quality. So the revert rate, the amount of code that has to be fixed after it hits production is much lower when they write that code with AI. And then they figured out how to label and trace and audit all those changes and approvals, so that they are in compliance with all of their required compliance frameworks, whether those are Soc 2, HIPAA, etc. So I often get this objection from folks. They say, well, I'm in a Soc 2 environment, I couldn't possibly auto-approve PRs. But in fact, there are frameworks as long as it's in your risk policies, as long as it's in your code review policies, as long as it's auditable, queryable and defensible, you can do this within your compliance framework, although work with your security and compliance teams to figure out how this can work for you.