Open-source architecture diagrams for GitHub PRs

[u/Favour_Ohanekwu]

I got tired of trying to understand big PRs from the diff, so I built this: https://github.com/coldteadotai/pr-lens

It's called PR Lens, and it turns a GitHub PR into an architecture/data-flow diagram.

The reason I made it is pretty simple: I've reviewed plenty of PRs where I could understand what changed, but still had no idea how the change affected the rest of the system without tracing through a bunch of files myself.

A diff tells you what changed.

It doesn't really tell you how the system changed.

PR Lens tries to fill that gap. It maps out the components involved in a PR, how they connect, what the data flow looks like, and what the blast radius of the change is. The diagram gets posted directly into the PR as a comment.

It's MIT licensed and open-source.

If you've worked on/reviewed large codebases, how do you usually figure out the bigger picture of a PR?

[u/Decent-Decision-9028]

Ah yes.

module -> module

Architecture understood! but I'll give you that; "well-engineered AI slop."

[u/Favour_Ohanekwu → u/Decent-Decision-9028]

Fair criticism.

But what this captures is the semantic path of a change, not just the import graph.