I still don't like the fact that AI is adding more stuff for us to read, it's accelerating the code production but slowing down the code review. I built my own code reviewer as well (https://pyor.review/), surfacing the important stuff first is the right track, but adding more stuff to read is daunting, but asking AI to just point you to what you need to focus on and skim the noise is what I'm leaning more towards.

▲

ramoz 6 hours ago | parent [-]

I don't think your sprinkled AI hints help your pitch if they immediately show injected into the diff.

Also, I think the guided review presents the opportunity to skim the code versus read the full diff - as semantic overview of multiple files/diffs, as well as file change description, give you the opportunity to green light anything you don't really need to read into, or give you enough context that you should dive in. i.e. https://x.com/thdxr/status/2073238046296924466?s=20

	▲	othmanosx 13 minutes ago \| parent [-]
		Thanks for the review, that's really good feedback. as we slowly read the code less and less, it only makes sense for AI to help us skim it more, until it becomes good enough for us to not read the code at all. still, on the other hand, do you think AI can tell you what a 5 word long function does in 5 words? probably not, so reading the code itself will stay faster than reading the summary, AI can only help alerting you on what it thinks is a potential bug, or same code moving around.