what-did-i-get-done
Skill13 starsChanged 58 days agoMITView on GitHub
Summarize authored commits over a user-specified time period into a concise update
10 other projects use a version of this, 5 of them edited.
Adopted by
Most recently taken up by
- upamune/skillsedited, first seen Nov 15, 2026
- Yeachan-Heo/oh-my-claude-sisyphustheir own version, first seen Nov 8, 2026
- Yeachan-Heo/oh-my-claudecodetheir own version, first seen Nov 8, 2026
- ArchitektApx/cursor-skills-for-claudeedited, first seen Nov 1, 2026
- michielvandermeer/skillstheir own version, first seen Nov 1, 2026
- jonmumm/skillstheir own version, first seen Oct 21, 2026
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 5
- dhanji4U/skills★ 280% same
- jaydubya818/MissionControl★ 274% same
- ElyzeSolutions/skills★ 197% same
- upamune/skills★ 197% same
- ArchitektApx/cursor-skills-for-claude★ 097% same
Wrote their own version · 5
- Yeachan-Heo/oh-my-claudecode★ 41ksame name
- Yeachan-Heo/oh-my-claude-sisyphus★ 41ksame name
- michielvandermeer/skills★ 9same name
- malinskibeniamin/skills★ 4same name
- jonmumm/skills★ 3same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository84 other files it gives its agents.
- AGENTS.mdAGENTS.md
- architectSkill
- arenaSkill
- automate-meSkill
- babysitSkill
- benchmark-checklistSkill
- blast-radiusSkill
- broSkill
- browseSkill
- ceo-reviewSkill
- changelog-to-postSkill
- correctSkill
- create-formal-verification-skillSkill
- create-verification-skillSkill
- customer-lensSkill
- deslopSkill
- engineer-modeSkill
- figure-it-outSkill
- fix-ciSkill
- fix-merge-conflictsSkill
- founder-modeSkill
- founder-voiceSkill
- fstackSkill
- geo-pageSkill
- get-pr-commentsSkill
- howSkill
- inbox-triageSkill
- interrogateSkill
- in-your-own-wordsSkill
- ketchupSkill
- lead-replySkill
- maintain-formal-verification-skillSkill
- maintain-verification-skillSkill
- make-pr-easy-to-reviewSkill
- no-commentsSkill
- office-hoursSkill
- poteto-modeSkill
- principle-attack-the-premiseSkill
- principle-boundary-disciplineSkill
- principle-build-the-leverSkill
- principle-clear-namingSkill
- principle-encode-lessons-in-structureSkill
- principle-exhaust-the-design-spaceSkill
- principle-experience-firstSkill
- principle-explain-the-numberSkill
- principle-fix-root-causesSkill
- principle-foundational-thinkingSkill
- principle-guard-the-context-windowSkill
- principle-laziness-protocolSkill
- principle-make-operations-idempotentSkill
- principle-migrate-callers-then-delete-legacy-apisSkill
- principle-minimize-reader-loadSkill
- principle-model-the-domainSkill
- principle-never-block-on-the-humanSkill
- principle-outcome-oriented-executionSkill
- principle-prove-it-worksSkill
- principle-redesign-from-first-principlesSkill
- principle-separate-before-serializing-shared-stateSkill
- principle-sequence-verifiable-unitsSkill
- principle-subtract-before-you-addSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 9 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
Read commits authored by the current git user email within that range.
- Distinctive: line 26
Do not infer intent or motivation.
“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
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
- 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
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

