mcpField
W
what-did-i-get-done

what-did-i-get-done

github.com/yeachan-heoOther40.7k8 installsUpdated today
Repository

About what-did-i-get-done

What Did I Get Done is a skill for summarizing authored work from Git and pull-request records. It groups changes by outcome and reports supporting evidence, counts, and unfinished work.

Key features

  1. 01Collects commits and merged pull requests
  2. 02Groups contributions by outcome
  3. 03Reports commits, net lines, and tests
  4. 04Separates unfinished work
  5. 05Links themes to commit ranges

Use cases

  1. 01Prepare a weekly work summary
  2. 02Review contributions across repositories
  3. 03Identify open work that still needs completion

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/yeachan-heo/oh-my-claudecode --skill what-did-i-get-done

After installing, type/what-did-i-get-donein Claude Code to confirm it loaded.

Details

From the project README

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.

Comments

Markdown supported