spawrks2 hours ago
In my experience there is something beneficial about having a different context review and prompted differently, but it's not used very well in practice. Your previous context does create its own blind spot, but you're also getting at a problem in non AI reviews which is "what am I reviewing for?". Some companies like Google have traditionally had very tight guidelines for what a PR reviewer is supposed to criticize and what not to worry about, I don't think AI code review is much different on this topic
- swimmingpolaran hour ago
  With that, we're back to square one again. Why not just provide that set of guidelines, prompts, and skills locally, which is very likely something modern LLMs can already handle?
  Can't really see the point of settings up a separate AI code review step and make that into some sort of stage that everybody pretends to care. Just to make it look like something extra is, hopefully, happening?
  Plus, I feel like any previous context a developer had before submitting the PR must have the most accurate context rather than a code review AI.
  It's more on pure curiosity than ranting.
mukundzha62 hours ago
I dont use ai code reviewers. I personally use this tool very frequently before making any commit to github :- https://github.com/mukundzha/avouch
blinkbat2 hours ago
Cut velocity and increase supervision
buffer_overlord2 hours ago
Nope I always ignore it
deadcatfound2 hours ago
[flagged]