"I pay Claude, to use Claude, to write instructions for Claude, to review code from Claude" Have we all just given up?
Show HN: adamsreview – better multi-agent PR reviews for Claude Code
11–20 of 71 posts
Re: Show HN: adamsreview – better multi-agent PR reviews for Claude Code
#12The 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.
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
#13"I pay Claude, to use Claude, to write instructions for Claude, to review code from Claude" Have we all just given up?
Re: Show HN: adamsreview – better multi-agent PR reviews for Claude Code
#14Re: Show HN: adamsreview – better multi-agent PR reviews for Claude Code
#15Re: Show HN: adamsreview – better multi-agent PR reviews for Claude Code
#16We seem to be fighting complexity with complexity. Does it really help?
I wish I was kidding…
Re: Show HN: adamsreview – better multi-agent PR reviews for Claude Code
#17The 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.
Re: Show HN: adamsreview – better multi-agent PR reviews for Claude Code
#18Re: Show HN: adamsreview – better multi-agent PR reviews for Claude Code
#19Re: Show HN: adamsreview – better multi-agent PR reviews for Claude Code
#20Why 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.
You’re right though, but evals are actually fairly tricky to write and maintain.