Live data from Hacker News

Show HN: adamsreview – better multi-agent PR reviews for Claude Code

github.com

11–20 of 71 posts

Re: Show HN: adamsreview – better multi-agent PR reviews for Claude Code

#12

The best code review improvement I have done in my workflow with Claude is using tuicr ( https://tuicr.dev ). It runs locally, YOU review all the code locally, and feedback that to Claude. Agents reviewing AI code always felt dirty to me, especially when working on production (non-disposable) code.

The video actually convinced me that this might be an interesting tool. I'm going to try it myself for a small one-shot project and see how well it performs.

TUI-based reviews on it's own are already interesting. I had never considered it, I guess.

Re: Show HN: adamsreview – better multi-agent PR reviews for Claude Code

#14
the irony of multi-agent code review is that the people who would use it are already the ones who care about code quality. the real problem is everyone else just hitting accept on whatever claude spits out without even reading the diff. tooling for review keeps getting better while the average review effort keeps going down.

Re: Show HN: adamsreview – better multi-agent PR reviews for Claude Code

#16

We seem to be fighting complexity with complexity. Does it really help?

This has been the gradual progression of the software world for the past half century, so it’s apt to use LLMs to fight LLMs and call it progress.

I wish I was kidding…

Re: Show HN: adamsreview – better multi-agent PR reviews for Claude Code

#17

The best code review improvement I have done in my workflow with Claude is using tuicr ( https://tuicr.dev ). It runs locally, YOU review all the code locally, and feedback that to Claude. Agents reviewing AI code always felt dirty to me, especially when working on production (non-disposable) code.

that's a good addition to fresh editor (also tui) and both rust

Re: Show HN: adamsreview – better multi-agent PR reviews for Claude Code

#20

Why not just use an eval harness to prove this catches more real bugs? Benchmarks on actual bug classes would be far more convincing than comparing against /review.

That’s probably more work than the entire repo itself. Would need to be something like SWE-bench with and without “adamsreview”.

You’re right though, but evals are actually fairly tricky to write and maintain.

Post reply on HN