what-did-i-get-done
Summarize authored commits over a user-specified time period into a concise update
- License 许可
- MIT
- 最近更新
- 2026-11-12
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- what-did-i-get-done
- description
- Summarize authored commits over a user-specified time period into a concise update
03 SKILL.md 正文
What did I get done
Read the portable runtime contract before following this workflow.
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
04 同仓库更多 Skills
why
Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.
wayfinder
Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
unslop
Cut AI tells from any writing.
universal-architecture
Apply responsibility-based architecture and enforce import boundaries. Use for code placement, architecture reviews, adapters, CLI entry points, platform sharing, and ESLint boundary rules.
typescript-best-practices
TypeScript best practices. Use when reading or editing any .ts or .tsx file.
triage
Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.