Obviously it relies on an LLM run to get true semantic groupings of what changes were done, and why, but can also be used without an LLM to get more mechanical groupings/group names of changes made, along with the right order to view them in. The manual tree-sitter parsed analysis is deliberately conservative for now, but if people want to avoid the LLM analysis I can spend more time on that.
You can use it for other peoples PRs, or for your own when you've relied heavily on Claude Code or Codex for that particular PR. If the change came from your own Claude Code or Codex session, it reads your prompts and marks which changes you asked for and which the agent decided on its own as well to help you validate it before submitting for others to review.
Demo video done on some public project PRs is in the repo; for a look at what it looks like when it pulls in information about your own claude/codex sessions you'll have to use it yourself for now, but I'll work on getting an example of that up soon so people can take a look before spending time to get this to work locally for themselves.
I also added support for perforce style side by side diffing because I always kind of liked it, though it's not quite as slick yet.