What Did I Get Done Skill for Claude
Summarize authored commits over a user-specified time period into a concise update
253 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
255
stars on the repo
on the repository, not the skill itself
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/michael-denyer/pstack-claude --skill what-did-i-get-doneThe instruction itself
5 sections, as written by the authorWhat 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
- Resolve the requested time window into concrete dates.
- Read commits authored by the current git user email within that range.
- Exclude merge commits and uncommitted changes.
- Synthesize the most important shipped changes into a concise status update.
- 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
How to use it
Copy the folder
Take michael-denyer/what-did-i-get-done from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
Check the name does not clash
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.