self-reviewlisted

Merged pull requests are the raw material. The note is the deliverable, and the user pastes it into their Lattice self review. A list of PR titles is a **changelog**, not an achievement summary. 339 merged PRs in one repo are maybe six things the user actually did. Your job is that collapse: from titles to themes, from commits to outcomes. A manager who skims the note must be able to name what the user owned. ## Resolve the range first The user says "since last november", not a date. Convert it before you query, and never type today's date from memory: ```bash today=$(date +%F) ``` Relative words anchor to that date. "Last November" from 2026-09 means 2025-11-01. When the phrasing has two readings - "last quarter" mid-quarter, "this year" in January - say which one you took in one clause, then carry on. State the resolved window on the note. A reader cannot judge "12 PRs" without knowing over how long. ## Collect the work Volume is the thing to get right here. A ten-month window runs to several hundred PRs, and a query that silently returns the first 100 hands the user a review that misses most of their year. `scripts/fetch-prs.sh` exists for that: GitHub search caps every query at 1000 results, so the script queries one month at a time, paginates inside each month, and dedupes the overlap. ```bash # run the script by its full path under this skill's directory scripts/fetch-prs.sh 2025-11-01 > "$TMPDIR/self-review-prs.json" # since, to today scripts/fetch