undefined | Better HN

0 pointsAIorNot5mo ago0 comments

I think we need better code review tools in the age of LLMs - not just sticking another LLM to do a code review on top of the PR

Needs to clearly handle the large diffs they produce - anyone have any ideas

0 comments

ngruhn5mo ago

I was about to write my own tool for this but then I discovered:

   git diff --color-moved=dimmed-zebra

That shows a lot of code that was properly moved/copied in gray (even if it's an insertion). So gray stuff exactly matches something that was there before. Can also be enabled by default in the git config.

paulhebert5mo ago

I would love if GitHub implemented this in their UI! There’s and issue: https://github.com/orgs/community/discussions/9632

erichocean5mo ago

I used autochrome[0] for Clojure code to do this. (I also made some improvements to show added/removed comments, top-level form moves, and within-string/within-comment edits the way GitHub does.)

At first I didn't like the color scheme and replaced it with something prettier, but then I discovered it's actually nice to have it kinda ugly, makes it easier to detect the diffs.

[0] https://fazzone.github.io/autochrome.html

godelski5mo ago

That's a great solution and I'm adding it to my fallback. But also, people might be interested in diff-so-fancy[0]. I also like using batcat as a pager.

[0] https://github.com/so-fancy/diff-so-fancy

VMG5mo ago

Perfect. This is why I visit this website

karczex5mo ago

Thanks:)

steveklabnik5mo ago

I personally agree with you. I think that stacked diffs will be more important as a way of dealing with those larger diffs.

alfalfasprout5mo ago

Yep, this pattern of LLMs reviewing LLMs is terrifying to me. It's literally the inmates running the asylum.

j / k navigate · click thread line to collapse