Post

I got an itch to play with some ideas I’ve had around code review. Also decided to completely vibe code it with Claude Code to become more familiar with the strengths and weaknesses of working like this. Idea is you can sort files topologically, and symbols modified in this PR are highlighted.

Sorting topologically is an excellent idea here. Seems like a painfully obvious improvement in retrospect! As the best ideas are. How does it handle things that are not part of the module graph? Eg a random md file

I think you could do even better than topological sorting if you had enough static information and calculate all of the paths through the modified code, so you could review logical flows individually. It has potential to grow explosively but that could be a signal the PR is too complex.

I really wish GitHub cared about the PR review experience enough to experiment like this. I feel like it hasn’t changed in around a decade. I suspect with agents writing so much new code the review process is going to quickly become the bottleneck.

ironically they are *slightly* changing it rn: github.com/orgs/communi...