// Use when opening a PR — produces a clean PR description (what / why / how to verify / risks) from a branch diff against base.
| name | pr-summarizer |
| description | Use when opening a PR — produces a clean PR description (what / why / how to verify / risks) from a branch diff against base. |
| version | 0.1.0 |
| status | experimental |
| risk | low |
| tags | ["engineering","read-only","writes-files"] |
| Name | Type | Required | Notes |
|---|---|---|---|
base | string | no | default origin/main |
branch | string | no | default current HEAD |
A markdown PR body with sections: Summary, Why, How tested, Risks, Linked.
git diff <base>...HEAD --stat and git log <base>..HEAD --oneline to see scopegit diff <base>...HEAD for contentFixes # / Refs # from commits.env* → STOP and surface; PR shouldn't include themUse when capturing an architecture decision so it survives turnover — produces an ADR-NNNN.md from context, options considered, and the chosen path.
Use when reviewing a proposed REST or GraphQL API change before merge — checks contract clarity, backwards compatibility, errors, pagination, auth, and naming.
Use when first encountering a new dataset — produces a structured profile (schema, missingness, distributions, outliers, gotchas) before any analysis.
Use after an incident is resolved — drafts a blameless postmortem from timeline notes, alerts, and chat threads.
Use when planning the next sprint — turns ticket intake + team capacity into a planned sprint with explicit non-goals.
Use after a session to promote useful episodic notes from logs/episodic/ into distilled, dated entries in MEMORY.md and memory/semantic/.