standup-summarylisted

Reconstruct the update from evidence, not memory. Git and the issue tracker already know what happened; the job is to translate that record into the three or four sentences a teammate actually wants to hear, at the altitude of outcomes ("shipped the retry logic for webhooks") rather than mechanics ("bumped a dependency, fixed a typo, refactored a helper"). ## Step 1: Establish scope - **Time window:** since the last workday for a standup, the last 5-7 days for a weekly. Confirm if unstated and ambiguous. - **Identity:** the git author to filter by - `git config user.name` / `user.email` in the current repo, unless told otherwise. - **Repositories:** default to the current one; ask whether other repos should be included when the user's request implies more ("what did I do this week" often spans several). ## Step 2: Collect the evidence Per repository: ```bash # Commits by the author in the window, all branches git log --all --author="<email-or-name>" --since="<window>" \ --pretty="%h %ad %s" --date=short # Branches touched recently git for-each-ref --sort=-committerdate refs/heads/ \ --format="%(committerdate:short) %(refname:short)" | head -10 ``` When `gh` is available and the repo has a GitHub remote, add the PR and review picture: ```bash gh pr list --author "@me" --state all --limit 15 \ --json number,title,state,updatedAt,isDraft gh search prs --reviewed-by "@me" --updated ">$(date -v-7d +%Y-%m-%d)" --limit 10 2>/dev/null gh issue list --assignee "@me" --st