Code review is broken. Not the tooling. Not the AI. The format.
Every engineering leader we talk to says the same thing: their team ships fast, their AI catches real bugs, their static analysis is dialed in. And yet PRs sit in inboxes for days. The bottleneck isn't quality. It's attention. It's vibes.
We spent six months studying how engineers interact with pull requests across 4,200 repositories. The data was clear. The median time a reviewer spends reading a PR before making an approve/reject decision is 14 seconds. Fourteen. The rest of the time logged against a review? Context switching, loading diffs, scrolling past generated files, reopening the PR three hours later to write "lgtm," and trying to remember what the PR was even about after getting interrupted by Slack.
Engineers already know what they think. They just need a faster way to say it.
Today we're launching SwipeReview™, a new interaction model for Augment Code Review that replaces the traditional diff view with short-form video summaries of every pull request. Swipe right to approve. Swipe left to request changes. Ship code at the speed of instinct.
How it works
When a PR is opened, Augment's three-agent architecture (coordinator, implementor, verifier) analyzes the change and generates a 15-to-60-second video walkthrough. The video includes:
- A narrated summary of what changed and why, delivered by one of six AI voice personas. Early access users overwhelmingly preferred "Calm Senior Engineer Who Isn't Mad, Just Disappointed," though "Enthusiastic Junior Dev" has a dedicated following.
- An animated diff highlighting the most significant modifications, with smooth transitions and a subtle particle effect when a function is deleted.
- A risk score overlay, displayed as a glowing ring around the PR author's avatar. Green is safe. Red means someone touched the payments service.
- A soundtrack matched to the complexity of the change. Minor dependency bumps get lo-fi beats. Breaking API changes get Hans Zimmer-style horns. We licensed a catalog of over 4,000 tracks. A PR that modifies both the database schema and the CI pipeline will trigger what our audio team calls "the full Dunkirk."
The reviewer watches the video in SwipeReview's mobile-first, vertical-scroll interface and makes a decision. No comments. No nitpicks. No "just one small thing" threads that balloon into 47 messages over three days and end with someone mass-approving everything at 5pm on Friday.
If you want to leave feedback, you can record a voice memo, react with an emoji, or use our new "stitch" feature to record a response video overlaid on the original PR walkthrough. We found in early testing that engineers are 3x less likely to be passive-aggressive in audio than in text, though the data on emoji reactions is still inconclusive. One team used the skull emoji to mean "this code is dead to me." Another used it to mean "great job." We are monitoring this.
Why video
This isn't a gimmick. It's backed by research.
Engineers already consume the majority of their technical learning through video. Conference talks. YouTube tutorials. Twitch streams of people debugging production incidents at 2am. The mass migration to short-form video content is the single largest shift in information consumption in human history, and somehow the software industry decided it didn't apply to them because diffs are sacred. Diffs are not sacred. Diffs are a rendering choice made in 1991.
Our internal study found that SwipeReview reduced median review turnaround from 26 hours to 4 minutes. Approval rates held steady at 94%, which is roughly where they were before, because we all know what's happening. Most PRs get approved. We just removed the ceremony.
More importantly, engineer satisfaction scores increased by 41%. Several participants described the experience as "addictive." One staff engineer reviewed 200 PRs in a single sitting and described it as "kind of meditative." We have not yet determined whether this is a good thing.
The algorithm
SwipeReview includes an optional recommendation engine. Based on your past review patterns, code familiarity, and current energy level (inferred from your calendar density, Slack response latency, and how many times you've reheated your coffee according to your smart mug API integration), it prioritizes which PRs to show you and when.
If you've been in back-to-back meetings all afternoon, it will surface the low-risk PRs first. If your Slack status is set to 🎧, it will hold the breaking changes until morning. If you've swiped left on more than four PRs in a row, it will pause your feed and show a short breathing exercise. We call this Responsible Review™.
We are aware of the comparison people will make. We leaned into it. The interface is vertical. It auto-advances. There is a "For You" page. There is a discovery tab where you can browse trending PRs from public repositories. Our design team debated this for weeks and concluded that fighting a UI pattern used by 2 billion people daily was not a hill worth dying on. They then added a double-tap-to-approve gesture, which no one asked for and everyone immediately loved.
Social features
SwipeReview supports team-based review sessions, which we call Watch Parties. An engineering lead can broadcast a PR to their team and collect reactions in real time, creating what one beta tester described as "a code review that felt like a live podcast." We are told this is a compliment.
PR authors receive a "Wrap" at the end of each quarter summarizing their top-reviewed changes, most common approval speed, and a superlative chosen by their peers. Examples from the beta include "Most Likely to Refactor on a Friday" and "Best Use of a Ternary Operator in a Context Where a Ternary Operator Was Not Warranted."
Pricing
SwipeReview is included in all Augment Code Review plans at no additional cost. The AI-generated soundtrack feature requires the Enterprise tier. If your team would like their own voice cloned for internal PR narrations, please contact our sales team.
What's next
We're already working on SwipeReview for incident response (swipe right to acknowledge, swipe left to escalate), SwipeReview for architecture decision records, and a duet feature where two engineers can review the same PR simultaneously and compare their reactions in a split-screen format.
Long term, we believe every artifact in the software development lifecycle should be consumable in under 60 seconds on a phone while standing in line for coffee. Design docs. Postmortems. Quarterly planning. If it can't survive the scroll, it doesn't deserve the attention.
We know some people will read this and feel uncomfortable. That discomfort is a signal. The way we build software is changing, and the teams that adapt fastest will ship the most. SwipeReview is not the end of thoughtful engineering. It is the beginning of honest engineering: engineering that finally admits how reviews have worked all along, and builds a product around the truth.
Written by
John Edstrom
Director of Engineering
John is a seasoned engineering leader currently redefining how engineering teams work with complex codebases in his role as Director of Engineering at Augment Code. With deep expertise in scaling developer tools and infrastructure, John previously held leadership roles at Patreon, Instagram, and Facebook, where he focused on developer productivity and platform engineering. He holds advanced degrees in computer science and brings a blend of technical leadership and product vision to his writing and work in the engineering community.