/what-did-i-get-done

name: what-did-i-get-done
description: "Summarize authored commits over a period, grouped by theme with commit-range evidence, mechanical churn separated, and unfinished branches named. For standups and 'what did I get done'."
aliases: []
metadata:
  credits:
    authored-work-summary: pstack
    author: Lauren Tan
    url: "https://github.com/cursor/plugins/tree/main/pstack"
    port: pstack-claude
    port-author: Michael Denyer
    port-url: "https://github.com/michael-denyer/pstack-claude"

What Did I Get Done

Summarize authored work from the record, not from memory.

Workflow

1. **Establish identity and window**: which author(s) and what period (default: the last 7 days; take the user's override). 2. **Collect**: `git log --author=<you> --since=<window> --stat` across the repos in play; include merged PRs via `gh pr list --author <you> --state merged --search "merged:>=<window-start>" --limit 500` where the user cares about review surface (`--state` defaults to `open`, so it must be named; `--author` needs its value; the default limit of 30 silently truncates a busy window — pass an explicit limit or paginate until a page comes back short). 3. **Group by theme**, not by commit: a theme line names the outcome ("auth retry hardening"), the commits underneath are the evidence. 4. **Count honestly**: commits, net lines, tests added. Mechanical churn (renames, lockfiles) is grouped separately or left out, never passed off as progress. 5. **Started-but-unfinished**: branches and PRs opened but not landed in the window, each with what remains — the section standups actually need.

Rules

• Every theme line links its commit range; no theme without commits.
• No inflating: a revert-pair counts as zero, and that is said, not hidden.
• The summary is prose over a small table; it fits in one screen.