PR Lens is a new way to look at code. It draws animated architecture and data flow diagrams of any codebase and every pull request, so you see the change before you read a single line of code. It runs as a GitHub Action, on the CLI, or as a skill for your coding agent. Open source under MIT.
Agents write more code every week, but we still have to understand it, and reading it line by line is no longer an efficient way to do that.
We need new ways to look at code.
What if reading code was visual? A few hundred lines a minute, leaving your attention for the part that's critical: the mental model of the system you maintain, its architecture, how it evolves, and how data moves through it?
This is why we built a custom renderer for agent-written diffs.
Every pull request comes with an animated architecture and data flow diagram. Changes, additions and removals are colour-coded, and it moves, so you watch a request travel through the system rather than a wall of diff.
It's open source under MIT, works with any model you bring, and runs as a GitHub Action, on the CLI, or as a skill for your coding agent. The repo is here: github.com/coldteadotai/pr-lens
the mental model part really hits. i run a few claude code agents in parallel worktrees, and after a day of merges i genuinely lose track of what moved where. scrolling the diff doesn't fix that. "watch the request travel through the system" is exactly what i keep wishing for.
adding the skill and pointing it at my last messy PR, THANKS for shipping this 👍
I think the biggest shift here is treating code review as a comprehension problem, not just a line-by-line comparison problem. That feels increasingly important as AI-generated PRs get larger.
Keeping an evolving baseline of the codebase and visually diffing each PR against it is such a clever review mechanic, excited to see where this goes!
This solves a real problem with agent PRs. I run a project with AI agents playing games against each other, and after enough agent commits I lose track of what changed.
I'm a solo founder, so really don't do PR's ... so the review workflow isn't my problem. My problem is that after a long run of agent written changes across a Rust desktop app, a C# API and a React front end, I quietly start losing the shape of my own codebase. The parts I wrote myself I can still see. The parts I directed, less so.
Does the baseline let you look at the system as it stands right now, rather than at what a particular change moved? And does it cross language boundaries? For ex a Tauri command in Rust and the TypeScript caller on the other side of it? Or is the diagram scoped per language?
This solves a real pain we hit building automation workflows: agents generate diffs faster than any human can read them, and the actual review bottleneck isn't diff size, it's building a mental model of what moved. Curious how the diagram holds up on changes that touch config/infra files versus pure logic changes, those tend to have very different "shapes" and I'd guess harder to render meaningfully. Starred the repo.
PR Lens is the part I want. I ship solo with a coding agent and the hard bit is understanding what it changed before I merge. Does it make sense with no second human reviewing, or is it built for teams?
This is such a fantastic way to review PRs! Sifting through hundreds of lines just to grasp what actually changed can be a real drag 😅 Getting a glimpse of the architecture and data flow first adds that crucial visual element that often feels absent between the PR desscription and the code itself. Plus, the combination of the GitHub Action and the open source aspect makes it even more intriguing. I am definitely eager to see how it perrforms with larger codebases.
Cool this will really make review process faster and this is kind of AI showcasing its own code right so how reliable this will be? Like will LLM's intelligence is used to showcase in node base structure or this process are hard coded by PR lens?
Or if you live in a coding agent: npx skills add coldteadotai/pr-lens, then ask it to
diagram the change it just made.
We use it in our workflow @Coldtea every day. Agents ship a PR; the diagram lands with it,
and I know what moved before I read a line of the diff.
About PR Lens by Coldtea.ai on Product Hunt
“See code through a new lens”
PR Lens by Coldtea.ai launched on Product Hunt on September 7th, 2026 and earned 336 upvotes and 27 comments, earning #1 Product of the Day. PR Lens is a new way to look at code. It draws animated architecture and data flow diagrams of any codebase and every pull request, so you see the change before you read a single line of code. It runs as a GitHub Action, on the CLI, or as a skill for your coding agent. Open source under MIT.
PR Lens by Coldtea.ai was featured in Open Source (68.8k followers), Software Engineering (43k followers), Developer Tools (519.6k followers) and GitHub (41.4k followers) on Product Hunt. Together, these topics include over 136.9k products, making this a competitive space to launch in.
Who hunted PR Lens by Coldtea.ai?
PR Lens by Coldtea.ai was hunted by fmerian. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Reviews
PR Lens by Coldtea.ai has received 3 reviews on Product Hunt with an average rating of 4.67/5. Read all reviews on Product Hunt.
Want to see how PR Lens by Coldtea.ai stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
fmerian
Hi PH,
Agents write more code every week, but we still have to understand it, and reading it line by line is no longer an efficient way to do that.
We need new ways to look at code.
What if reading code was visual? A few hundred lines a minute, leaving your attention for the part that's critical: the mental model of the system you maintain, its architecture, how it evolves, and how data moves through it?
This is why we built a custom renderer for agent-written diffs.
Every pull request comes with an animated architecture and data flow diagram. Changes, additions and removals are colour-coded, and it moves, so you watch a request travel through the system rather than a wall of diff.
It's open source under MIT, works with any model you bring, and runs as a GitHub Action, on the CLI, or as a skill for your coding agent. The repo is here: github.com/coldteadotai/pr-lens
I wrote about the reasoning and the design here: reducing cognitive load in AI-generated PRs
PR Lens is built by the team at Coldtea.
It takes a minute to run locally. Try this prompt: "Explain the codebase or the last change to me using pr lens". Send feedback :)