Loading summary
Transcript8 lines
- [00:00]
A
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 often, all the time. We 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 of PRs that I'm going to show you exactly how it gets done and we're going to get it done very quickly in this third 30 minute Howie AI mini episode. Let's get to it.
- [01:25]
B
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 copilot needs to see your entire codebase. Your chatbot needs to search across internal docs. And for enterprise buyers, that raises serious scale 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 WorkOS comes in. WorkOS gives you drop in APIs for enterprise features so your app can become enterprise ready and scale upmarket faster. Think of it like stripe first enterprise features. OpenAI, perplexity and cursor are already using Work OS to move faster and meet enterprise demands. Join them and hundreds of other industry leaders@workos.com start building today.
- [02:35]
A
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. So 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 2x3x 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 and D organization. Yes, they want to get those PR cycle time down and those reviews out quickly. But what they really think and what they've proven with their 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 SOC2, HIPAA et cetera. So I often get this objection from folks. They say, well I'm in a Soc2 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 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. So I really love just this whole concept. I also took some inspiration, who took inspiration from Intercom on this rewind bot, which is a little bit more of the technical way that they review PRs. And so this blog post about Diff Vader, which I love, shows a couple components of how they've scored risk. Whether it's blast rating is how correct it is, if all the actions have run, et cetera. And so between these two blog posts, I had a really good starting point for building an agent. I knew that I wanted to do this for chat prd. I knew we had a lot of low risk prs that were just sitting in the queue because my colleague and I were not getting to review them as kind of boring, especially a lot of like Devon authored PRs. And so this was going to be a really high impact thing that I knew I could build. And also let me work with a new framework that I'm excited to demo for you all here on how I AI. So we're going to go to this Codex Vibe coded deck and we're going to walk through how I built a code review risk scoring bot with Vercel's eve. So if you have not heard about eve, I'm a little bit obsessed with eve. Why do I like eve? Well, EVE has become the simplest way for me to deploy AI agents in the enterprise in Slack and GitHub, without the torture and pain of something like Hermes Agent or my beloved openclaw. So when I'm working and helping other companies sort of like think about how to deploy agents, if they're using Vercel, I tell them to use eve. Why do I tell them to use eve? Well, what's awesome about EVE is a lot of it is just a directory and EVE agent is very similar to openclaw. Just a directory of instructions, skills, code, and it can talk to you in channels that are out of the box in Vercel. So again, it's like very easy to set up the agent. It's very easy to give it skills which we all use. It's very easy to give it tools. It can even have a sandbox in which it can execute things, including your code, if you're doing a code review. And then my favorite part is managing, talking to the agent in specific channels and connecting it to enterprise data is super easy. So because Vercel has shipped a Vercel connectors, which are like managed connections inside your Vercel account, you can just literally go through like a little wizard to hook up Slack to your EVE agent, little wizard to hook up GitHub to go through your agent. And it's all set up, the refresh tokens, all that stuff. Everything that's painful about creating an agent is just taken care of and I sound totally like a vercel shill. I've just tried a bunch of stuff and this has been the easiest framework to get up and running. It uses the chat SDK behind the scenes and if you are creating any sort of chatbot in Slack teams, WhatsApp, whatever, I mean bless, I have. I was asking for this chat SDK for a long time. It got built. This is an open source framework that I think is so useful whether or not you use EVE or not to stand up a chatbot. It just like takes away all the complexities of managing like multi channel agents. It handles all like the Slack configuration. It gives you a manifest for Slack. Like I love it. The chat parity Slack bot and teams bot actually runs on the chat SDK but it's even better when it's bundled into this E framework. And so I highly recommend you try E framework again. Like, they didn't pay me to say this. I just really like it and I found it super easy to use. And now every agent that I'm creating that I want to interact with in Slack for an internal use case, if I don't already have an open claw, I'm porting over to eve. So how did I actually build this? What does the agent do? Well, I built it in Codex and so I'm going to show you the amazing prompt where I started this PR review bot which it says I want to make an internal GitHub bot slash app that reviews PRs after all C checks. That's checks are green and grades low medium high risk and approves the low rish. Oh my God, you guys, I can't type. I'll, I'll type this a versa. Low risk PRs automatically. That's all I did. And then I interrupted it. I steered it and said we could design it as a Vercel EVE agent if you want. And it said sure, that seems like a good, good idea. And it was off to the races. And so instead of going through kind of like the chat on Codex on how I built this, this took a couple turns, but really not that many. I would say a couple things that were like magical as I ran Codex is not that it did the code for the eat agent and the repo. That was fine. That was interesting. And I'll tell you a little bit about how the code actually works in a sec. But what was actually awesome is if you've ever set up a Slack bot or a GitHub app, you have to like click through a Bunch of configuration screens, you have to pick permissions, you have to do all this stuff. And so what I did is my favorite hack is I had it use Chrome browser use and I let it navigate Slack bot setup, I let it navigate GitHub set up and I just like clicked buttons in 2F aid and just double checked that it was right. And so I said, you know, is it configured yet? It said no, it needs to configure all this stuff in the permissions on the GitHub bot. I was like, great, you're logged into Chrome. And then I was like, I can press save. It was having a hard time press save. And so if you're just sort of like meta tip, if you ever have to do like complex SaaS configuration, set up an app, you're like, I'm fine writing code, but I don't want to do the configuration in somebody's third party service using Chrome browser use is such a useful hack to get that stuff done. So again, I just built this in Codex. I actually didn't give it any instructions on scoring, I didn't give it any instructions on configuration, I didn't give it any instructions on risk. I just said kind of like one ish shot it few shot this into production. And so I want to talk a little bit about what the agent does and how it works. So it's pretty simple. If you were building a PR review agent, this is what I would suggest suggest you do, which is it reads the pr, it looks at the exact DIF and it scores the risk and it publishes the evidence to the risk. If it's low risk, if it's assessed that it's a low risk pr, it submits an approval on the pr. If it needs a human, it escalates to human and if there's a blocking requirement then it stops and it will require a request change. So it's like very similar to how a human would do code review. How does it work from a technical flow perspective? So the GitHub, I have a GitHub app, it keys off an event after all of the PR changes are done. Vercel's GitHub integration picks that up in the GitHub Vercel channel and it sends it a little bit of information. Vercel spins up its sandbox, it checks out the repo, it runs it and looks at the diff. It runs a couple skills and tools to assess the risk and quality of the PR and then on the end it outputs like a thumbs up check, like it needs changes and A comment and then one fun thing that it does is after it does that, review it, it pings. My colleague and I in Slack to say this PR is ready for review or it needs some help. So if you were to set up your EVE agent to be similar to mine, what would it have? Well, it would have a couple things. It needs to have the GitHub channel, it needs to have instructions which I can show you a little bit of the instructions. It needs a skill to review the pr. It needs two tools. Read like all the files and information around the PR and then how to actually put a risk decision in. And then it has, you know, a couple things like a Slack notifier. So this is not that many files. It's pretty simple. I will show you our instructions just to make this like very clear how easy it is to set this up. It's a chat parity engineering agent. It reviews prs, it calls the risk context, it scores it and then it has a couple instructions. This is it. There's no scrolling, it is like four, four or five paragraphs, a couple bullet points and it's ready to go. You do not need to over engineer this. And it works really, really well. So this is again why I like this EVE agent framework. Because you're just working in natural Text or in TypeScript and it's super easy to implement. Setting up the GitHub app, you can ignore this. I mean, I guess like point your agents to this instructions. I did not do any of this. Again, Chrome browser use did this on our behalf. And so it just has to have access to the pull request, the contents of your files, CI checks and action checks and then some metadata. And I just had Vercel set all that up. It has a couple rules on when it's triggered, so you don't want it triggered on every PR before checks are done. So I kind of had to like reduce some noise in the PR rules. And then there's just two basically steps to this. It reads the pr. It's like a skill to read the pr. I will show it to you. It's not that thrilling. But again just showing you how simple it is. It reads and reviews the pr, it has a couple repo specific risk kind of categories. So like docs are low risk, feature logic is medium risk. And then like authentication billings high risk. Div size does not set risk. And then it gives some like instructions on writing. Again, this is it. It's like not that much, maybe one page of text. I did not write any of this. I refined it and so what I'm trying to reinforce to you is like writing these agents is not that hard. It is literally just writing instructions and skills. That is what it takes to create an agent like this. And that's why I like this Efraim work, because you can do a lot of it in markdown and then once it reads the code, it scores the risk. And so it looks at six things. How big is the change? Surface and blast radius. Is it easily reversible? Right. Like a huge data migrations may be harder to reverse. Does it touch data security and does it cover data security? Does it change anything about our operations? And verification gap is like, are our tests complete? Did CI complete? Can we actually test a couple ways that this is true? And then it has sort of like a script that it runs to calculate a score and then anything under 24 points. Again I did not like choose these thresholds. Anything below 24 points is low risk, medium risk is 25 to 64 and then 65 and above is high risk. Medium and high risk PRs require human approval. So it's pretty simple. There's some logic in here to only review the latest changes, which I like. And then the final piece is it escalates us to us in Slack for final action. So we have repo rules probably very similar to all of you. That requires a review in our GitHub to like match all of our rsoc2 compliance requirements. It just makes auditing and management of our compliance really easy. I went through a couple ways where the bot could like quote unquote, act like a human to do the review. It just didn't seem worth it. So what it does is escalate to Slack and then it says this one's been automatically reviewed. You can punch the approve button and merge and you're good, good to go. And so we sort of like built in an operational process here as well. But let's see what this actually looks like in action. So I have three PRs for you just to show you kind of how this works. Now the, the PR bot's called Merge Mommy. She is Merge Mommy, the PR review bot. You know when you make internal bots, we don't have div, we have Merge Mommy because we're fun@chat prd. And this was a docs only update automatically done by Devin. And typically I just like smash the approval button on these, merge them. But I found that like we were just getting queued up of a lot of docs changes that didn't really need a bunch of review and so what happens on Once the PR is ready to go, Merge Mommy runs it gives a risk score, 6 out of 10. It's very low risk because it only changes docs, but it's not auto approved because it has merge conflicts. So that's one of the scoring issues it has to check. And then there are some detailed notes here about why it's blocked in the approval. Blocker is the pull request has merge conflicts. A cleaner example here is the stock which I already merged, which again went through and said it's 7 out of 10 low risk, it's auto approved. And you can see up here, Merge Mommy gave a little check that said it's approved. Now what we do with these approved PRs, as I said, is we send them to a Slack channel. And so the Slack channel says, hey, either of you can take this, approve it. The risk is low, the checks are green, you just need to smash that approve button and merge it.
- [19:04]
B
So.
- [19:04]
A
So it's just like a really nice automated flow. Now why do we have to have a human do it? As you can see, this check mark is gray. A bot cannot actually meet our repository rules for required approval. And so we can either skip those rules, hack around it. We just decided this check would be a signal that our humans can approve it without really looking at it and then merge it as we want. And then let's show one where Merge Mommy did not approve it. This is a deprecation PR. So we had chat v1 and chat PRD and we're moving to chat v2. We kind of like refactored a bunch of code, but we left the old stuff behind a feature flag and it was like ready to delete. So there's like 35 changes, Big Red diff that we wanted to delete. And you can see here Merge Mommy. I'm sorry, I can't take myself seriously when I say it, but I'm going to say it anyways. Merge Mommy gave it a 45 out of 100, a medium risk. And it was not approved by a human because both it had some code issues as well as the policy said it changed server API behavior. It was a large change service and so it's medium, not low. And it can't approve the pr. Now we can run this against every PR that goes through our process. And again we're going to just keep getting these notifications in Slack that just let us know, hey, this can be approved or this requires human review. Again, I like to say this thing where we can put AI to work for us or we can have AI put us to work. And this is an example where you do both. I've put AI to work this lovely EVE agent. I put AI to work to review and score the PR and tell me if there's any risk and like be detailed eyes on it. And then I have AI put me to work by escalating into Slack for the final action and making it like a two click process to get this thing to production. Now I just have to say this is something that I was really intimidated to build. I thought this was going to take me like days and days and days. I was like, I don't want to set up the GitHub app. I actually had tried this before codecs like browser use was really good and before the EVE agents had come out and it was just like not easy to do. But now that we have these open source frameworks, now that we have these agent building frameworks, now that kind of like everybody's agreed that we need Slack bots that do AI, a lot of these problems have been solved. And then Codex browser use was just like the cherry on top that made building this agent super, super, super simple. So to just recap for you all in this lightning fast mini episode about how to build a PR risk score and review bot use, Vercel's EVE agents give it instructions and a skill to read a PR and calculate a score based on a couple components. Hook up that vercel agent to GitHub into Slack, let it read from GitHub and give you a little gray check for approval and then have it slack you in Slack for that final human review and merge and your cycle time will be super, super fast and your PR velocity will go through the roof. Now I want to hear from you all, is this crazy? Can you pull this off at your company? And what would you put into your risk scoring that I haven't thought of? The final bonus piece off this, which I didn't show, but a lot of great folks do, especially the folks at Intercom do as part of this process is they run evals on this internal agent. So every time this review is run, it gets logged into. I think it's like an internal eval platform and an engineer looks at it and says, did the agent get this right? Did the agent get this wrong? Are we happy with the scoring mechanism? So very similar to how you'd use evals to improve your customer facing AI products, you're going to want to use evals to improve your internally facing AI bots, especially ones that touch really critical things like code. That has been my mini episode on how to build a PR approval and review bot here at How IAI AI. I cannot wait to hear if you think this is crazy or this is the way of the future. Thank you so much for joining and we'll see you soon.
- [23:46]
B
Thanks so much for watching. If you enjoyed this show, please like and subscribe here on YouTube or even better, leave us a comment with your thoughts. You can also find this podcast on Apple Podcasts, Spotify or your favorite podcast app. Please consider leaving us a rating and
- [24:01]
A
review which will help others find the show.
- [24:04]
B
You can see all our episodes and learn more about the show@howiaipod.com See you next time.