Why GitHub + dassi
GitHub is already where the work happens. dassi adds the missing layer: it can read what’s on the page and then take actions (draft, classify, fill, log, summarize) without you rebuilding context in a chat box.
What to automate in GitHub
- Inline PR diff explanations: Explain changes hunk-by-hunk and flag risk hotspots (auth, permissions, rate limits).
- Keyboard shortcuts for queues: Navigate PR lists and review queues more efficiently with safe bindings.
- Docs playground workflows: Turn documentation snippets into runnable playgrounds and validate behavior quickly.
Quick start
- Open GitHub in Chrome.
- Open the dassi sidebar.
- Start with a safe workflow: summarize → propose → draft → review → act.
Prompt recipes (copy/paste)
- “Explain what changed in this PR, inline per diff section.” (from GitHub PR That Explains Its Own Changes)
- “Flag any auth, rate-limit, or permission changes as high risk.” (from GitHub PR That Explains Its Own Changes)
- “Add J/K navigation for this list and Enter to open the selected row.” (from Keyboard Shortcuts for Any Web App)
- “Bind Shift+R to open review notes, but never trigger Delete.” (from Keyboard Shortcuts for Any Web App)
- “Make this code sample runnable and show output below.” (from Documentation With an Interactive Playground)
- “Change the example to match my API key and endpoint.” (from Documentation With an Interactive Playground)
- “In GitHub, explain this change inline per diff section and flag auth/permission risks.”
- “Create a review checklist for this PR: tests, edge cases, backwards compatibility.”
- “Turn this docs snippet into a runnable example and show output below.”
Safety checklist
- Tell dassi: “Never submit/send without confirmation.”
- If the page contains sensitive data, ask for redaction or aggregated outputs (totals-only, no PII).
- Prefer reversible actions first (drafting, labeling, notes) before destructive ones.