How We Built a Context-Aware Review Bot That Transformed Our Code Reviews
How We Built a Context-Aware Review Bot That Transformed Our Code Reviews
October 27, 2025
Read Time: ~3 minutes
At Tilt, we seek individuals who challenge personal assumptions, value ownership and trust, and strive for excellence to inspire and empower their team. If this article connected with you, join our team!
Originally presented at LeadDev in partnership with Augment Code
At Tilt (formerly Empower Finance), code reviews are critical to maintaining quality across our fintech platform. But like many engineering teams, we faced a familiar challenge: reviews were time-consuming, feedback was sometimes inconsistent, and engineers spent valuable time on repetitive review tasks that could easily be automated.
That's why we built a context-aware review bot using Augment Code, the results have been transformative.
(AI Gen) How We Built a Context-Aware Review Bot That Transformed Our Code Reviews - Tilt Engineering | Spotify
The Challenge
Our engineering team needed a solution that could:
- Understand our specific codebase patterns and conventions
- Provide consistent, high-quality feedback on pull requests
- Free engineers to focus on architectural decisions rather than style nitpicks
- Maintain high standards for code quality without slowing down velocity
Enter Augment Code
We chose Augment Code for its industry-leading context engine. Unlike other AI coding assistants, Augment doesn’t just look at individual files, it understands your entire codebase, your team’s conventions, and your architectural patterns.
Building the Review Bot
In my recent presentation with LeadDev, I walked through exactly how we built this system. The key was leveraging Augment’s deep codebase understanding to create a bot that doesn’t just check syntax, it understands our code.
How Tilt’s review bot transformed its code reviews, with Augment Code - YouTube
Tap to unmute
How Tilt’s review bot transformed its code reviews, with Augment Code LeadDev
LeadDev53.5K subscribers
The Results
Since implementing our Augment-powered review bot, we've seen:
- Faster review cycles: Automated checks catch common issues immediately, reducing cycle time by up to 40%
- More consistent feedback: The bot applies our standards uniformly across all PRs
- Better use of engineer time: The team focuses on architecture and complex logic, not style issues
- Improved code quality: Issues are caught earlier in the development process
Key Takeaways
- Context is everything. Generic AI tools can’t understand your specific codebase. Augment’s context engine makes all the difference.
- Augmentation, not replacement: Our review bot augments human reviewers, it doesn't replace them. Engineers still make the final decisions.
- Continuous improvement. As our codebase evolves, Augment’s understanding evolves with it.
Want to Learn More?
Watch the full video on LeadDev to see the bot in action and learn how we built it.
Interested in trying Augment Code for your team? Visit augmentcode.com to get started.
About James Garrett
I'm James, a seasoned backend developer with interest in crafting solutions on the C#/dotnet stack, scalability and performance challenges are my favorite. My career in software development has been a combination of startups and Fortune 500's with startup like cultures. Mid week you’ll find me coding away, but weekends are time for fishing, hiking, boating— anything outdoors!
In my toolbox, JetBrains Rider, macOS, The Azure Cloud platform and of course the best coding language (C#) are my preferred environment. Their intuitive interfaces and powerful features enhance my developer experience.
While I love software development, I don't find it particularly fun in a vacuum. The projects I've most enjoyed in my career are those where I get interact with a team to solve new challenges— that’s why I love it here at Empower.
What keeps me excited to come to work everyday is the fact we have a strong team based culture. Almost daily I’ll hop on a call with fellow Engineers or Product Managers to pair up on something. Culture isn’t an accident here, it’s an investment. Twice a year we bring the team together in person to get to know one another, learn what different pods are up to and form relationships.