The workflow, in plain English
Before: You open a 400-line pull request. You read the diff file by file, mentally inferring what each change does and whether it’s risky. 30 minutes for a thorough review.
After: Between each diff section, a collapsible blue box appears: “This block refactors auth middleware from callbacks to async/await.” Another one: “Warning: this removes the rate limiting check — was this intentional?” The PR taught you about itself. You review it in half the time.
Why traditional tools can’t: AI code review tools generate a summary at the top. Dassi injects explanations INLINE, next to the exact lines they describe.
Step-by-step
- Open a GitHub PR diff page.
- Ask dassi for inline explanations and risk flags.
- Skim section-by-section with the annotations as context.
- Leave comments or request changes with concrete reasons.
Example prompts to try
- “Explain what changed in this PR, inline per diff section.”
- “Flag any auth, rate-limit, or permission changes as high risk.”
- “Suggest review checklist items for this PR.”
Tips for better results
- Be specific about what you want injected into the page (buttons, filters, a panel, a summary, etc.).
- If the page has multiple sections, tell dassi exactly what to focus on (e.g., “the transactions table” or “the diff for file X”).
- Prefer safe workflows first: draft, summarize, label, and prepare — then take actions (submit, purchase) only after review.