logoalt Hacker News

Use AI for reviewing code especially when the diff is huge

5 pointsby simianwordstoday at 8:24 AM5 commentsview on HN

Comments

cadamsdotcomtoday at 10:52 AM

You can radically reduce your review burden but you can’t eliminate it - review is the part where you make your code good.

But whatever you see in review, you must add to a review checklist for the agent. You do this so you never have to check for that thing again.

Example: https://github.com/cadamsdotcom/CodeLeash/blob/main/.claude/...

(Use AGENTS.md or whatever agent docs you use, to tell your agent to review after it’s done working but before it stops.)

Congratulations! After you added hundreds more items to the agent’s review checklist, that work you did to build the checklist has automated the first 90% of the work. The second 90% is still.. reviewing the code. So no, you can’t escape code review.

It’s an asymptote. And it’s part of your job as a professional.

voidUpdatetoday at 10:28 AM

I can't tell if the title is a joke or not, the article seems to give some very good reasons why you shouldn't use an LLM to review pull requests

loloquwowndueotoday at 10:36 AM

If someone asks you for a code review and you turn your LLM loose to do it - you’re doing nothing. Just tell the requester you can’t be bothered and have them ask their LLM to do the review directly.

Relaying one LLMs output to another is very poor use of a human’s time.

show 1 reply
meander_watertoday at 10:40 AM

> I don't think you should waste time reviewing every single line of code in here and just use AI to review it!

> What you bring is the knowledge that the author nor the LLM doesn't know.

How can you possibly know what relevant context to provide the LLM unless you read the 10k loc? Now you've wasted double the time.