points by jayknight 4 hours ago | 0 comments
I mean if it's a code review, you gotta review the code.
[–] johannes1234321 4 hours ago
[–] karakrakow 3 hours ago
I've been trying to auto generate diagrams on PRs I'm reviewing. Flows changes via sequence diagrams, state changes and schema changes, post it to the PR with a skill. Then look at the relevant code based on the diagrams. Then \code-reviews. Moderately helpful. YMMV
Also mind: one doesn't only have to review changes code, but also review what hasn't been changed (are preconditions of other code still met?)