Hacker News Reader

we have a same rule for agents and humans, make a onepage html or a short deck with revealjs, not just the diff.

but the thing is most of the time it's not about what the feature contains or is the feature working? (we have a live preview env where we can try the feature)

it's more how can we make sure in the thousands of rows/changes that we are reviewing every day we don't have invisible issues while keeping the code standards we expect

fair, the html only proves the author understood it. tbh i still check every pr myself, just at the report level. a hook generates it, so it does not depend on the author writing well.

what a report cannot show, a separate auditor agent hunts for, with no stake in the pr getting merged.

Reply on news.ycombinator.com