What Did I Get Done
- 1.4k installs
- 2.5k repo stars
- Updated August 5, 2026
- cursor/plugins
what-did-i-get-done is a Cursor plugin skill that summarizes authored git commits over a chosen time range into a concise update for developers who need accurate session or sprint recaps without manual note-taking.
About
what-did-i-get-done is a Cursor plugin skill that produces short, high-signal summaries of completed coding work for a user-specified window such as yesterday, the last three days, or last week. The workflow resolves the requested range into concrete dates, reads commits authored by the current git user email, excludes merge commits and uncommitted changes, and synthesizes the most important shipped changes into a concise status update that includes the actual date range used. Developers reach for what-did-i-get-done before standups, weekly reports, or handoffs when chat history is incomplete but the git log holds the ground truth.
- Automatically summarizes completed work from git history, file changes, and commit messages
- Produces concise progress reports for standups, clients, or personal logs
- Reduces context-switching friction at the end of deep work sessions
- Works directly inside Cursor as a plugin with one-command invocation
What Did I Get Done by the numbers
- 1,408 all-time installs (skills.sh)
- +207 installs in the week ending Aug 5, 2026 (Skillselion tracking)
- Ranked #400 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/cursor/plugins --skill what-did-i-get-doneAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1.4k |
|---|---|
| repo stars | ★ 2.5k |
| Last updated | August 5, 2026 |
| Repository | cursor/plugins ↗ |
How do you summarize git commits for a time range?
Generate an accurate, human-readable summary of everything completed in a coding session without manual note-taking.
Who is it for?
Developers using Cursor who need fast, commit-grounded recaps for standups, weekly updates, or async status posts.
Skip if: Repositories without meaningful git history or situations requiring summaries of uncommitted local work.
When should I use this skill?
The user asks what they completed yesterday, last week, or over a specific date range and wants a git-commit-based summary.
What you get
Concise human-readable status update with date range and prioritized shipped changes
- Concise work-completion summary
Files
What did I get done
Trigger
Need a short, high-signal summary of work completed in a specific time range (for example: yesterday, last 3 days, or last week).
Workflow
1. Resolve the requested time window into concrete dates. 2. Read commits authored by the current git user email within that range. 3. Exclude merge commits and uncommitted changes. 4. Synthesize the most important shipped changes into a concise status update. 5. Include the actual date range used in the final summary.
Guardrails
- Be extremely concise and information-dense.
- Prioritize substantial behavior or architecture changes.
- Omit cosmetic-only changes (formatting, imports, minor renames).
- Do not infer intent or motivation. Describe changes functionally.
Output
- One short summary suitable for a status update
- Real date range
- Optional 2-5 bullets for major changes only
Related skills
Grill MeHave an agent relentlessly pressure-test their plan or design until every decision branch is resolved and shared understanding is reached.691k196kGrill With DocsPressure-test architecture decisions against their live codebase and living documentation before writing production code.585k196k
Lark CalendarLet their coding agents read, create, and manage events inside Lark (Feishu) Calendar directly from natural language instructions.493kLark ImLet their coding agent send instant notifications, post updates, and receive commands directly inside Lark (Feishu) workspaces.493kLark ContactLet their AI coding agents read and write contacts, send messages, and manage user data inside Lark (Feishu).493kLark AttendanceAutomatically fetch and report daily attendance data from Lark (Feishu) into their own tools or agents.493kHow it compares
Choose what-did-i-get-done for commit-grounded recaps in Cursor; use changelog generators when you need formatted release notes from tags.
FAQ
What git data does what-did-i-get-done use?
what-did-i-get-done reads commits authored by the current git user email within the resolved date window, excludes merge commits, and does not include uncommitted working-tree changes.
What time ranges does what-did-i-get-done support?
what-did-i-get-done accepts natural windows such as yesterday, last three days, or last week, resolves them to concrete dates, and prints that range in the final summary.