Explain a GitHub pull request diff inline
A summary at the top of a PR tells you what it claims to do. An explanation next to each hunk tells you what it actually does — and where to look harder.
Before you start
Section titled “Before you start”New to Dassi? Follow the installation guide and model setup guide.
Open the pull request’s Files changed tab in Chrome. Expand any collapsed files you care about. Open Dassi alongside it.
1. Annotate the diff
Section titled “1. Annotate the diff”Read the diff on this page. For each changed file, add a short note next to the diff explaining what the change does in plain language, and mark it low / medium / high risk. Treat anything touching authentication, permissions, rate limits, payments or data deletion as high risk.Read only: do not comment, approve, request changes or edit anything on GitHub.2. Get a review checklist
Section titled “2. Get a review checklist”Based on the diff, list 5 things I should verify before approving, in order of risk. Include the file and line for each.Check the result
Section titled “Check the result”Open the two hunks Dassi marked highest risk and read them yourself; the annotation is a pointer, not a verdict. Confirm nothing was posted: the PR’s conversation tab should have no new comment from you. Annotations disappear on reload.