alt Hacker NewsI am surprised of how many people here are claiming they review the results of multiple agents working on different prs at the same time constantly context switching between them.
I just focus on one, I use on purpose very short interactions because I want to check every single function directly and not a whole 300lines file or 2000lines pr just at the end. Probably I am going slower than most of you but I feel I retain the knowledge of my codebase almost as good as when I was the one writing the code directly, and my PRs get very few review comments
What get me tired the most is when people submit to me a pr to review and I see immediately they full vibe coded it and just delegate to me the actual hard work of correcting the nonsense written in it with a single prompt without interactions. The worst is when you ask someone why they implemented something that way and they answer with "well calude made it, I really didn't think about it, now that I read it it makes no sense indeed"
Replies
I'm similar. I work in a context where I am responsible for the code that is in production and need to know how it works and vouch for its correctness.
Even with short interactions though, the effort in reviewing adds up and I ended up building a tool to help with it: https://github.com/imron/crt
I can review in the tool, and it remembers which files I have seen/approved since a given commit, then I can leave comments against source code and have an agent pick up those comments over mcp so it has context when making corrections.
I’ve been assigning the copilot review thing on all of these PRs, but I’ve noticed lately it’s started writing really difficult to verify review comments. It would take you literally all day to understand and test the things it’s commenting to check if they actually are issues, so as a result we all just ignore whatever the copilot review says and no one does any review.
The entire point of 3000 line PRs is so that you can LGTM and not feel too bad about it
If someone sends you vibe coded code to review, then you are obliged to give them a vibe coded review answer right back at them. Make sure your vibe review prompt tells to agent to be as nit picky as possible. Maybe tell it to be intentionally contradictory with it's change requests. Keep answering with impossible vibe coded review answers when they get back to you and nothing else.
* insert melting face emoji here *