Back to Skills

what-did-i-get-done

Summarize authored commits over a user-specified time period into a concise update

3,899stars318forksUpdated 8/20/2026

Security Assessment

Safe(95/100)
Security Score95/100

About what-did-i-get-done

what-did-i-get-done is a small, focused skill that summarizes the commits you authored over a specified time period into a concise, high-signal status update. It solves the recurring chore of writing a standup or progress note by turning your own git history for a window like 'yesterday', 'last 3 days', or 'last week' into a short synthesis of what actually shipped.

The workflow resolves the requested time window into concrete dates, reads commits authored by the current git user email within that range, excludes merge commits and uncommitted changes, synthesizes the most important shipped changes, and includes the actual date range used in the output. Guardrails keep it useful and honest: be extremely concise and information-dense, prioritize substantial behavior or architecture changes, omit cosmetic-only changes like formatting or minor renames, and describe changes functionally without inferring intent or motivation. The output is one short summary suitable for a status update, the real date range, and an optional two-to-five bullets for major changes only.

It targets individual developers who need to report their recent work — for standups, weekly updates, or self-review. It is a thin, read-only skill: it only reads local git commit history and produces a text summary, with no writes, network calls, or external tooling, making it entirely benign.

FAQ

What does this skill produce?

A short, information-dense status update summarizing the commits you authored in a given time window, plus the real date range used and an optional two-to-five bullets for major changes only.

Which commits does it include?

Commits authored by the current git user email within the resolved date range. It excludes merge commits and uncommitted changes.

What time ranges can I ask for?

Any specific window such as yesterday, the last 3 days, or last week; the skill resolves the request into concrete start and end dates and reports the exact range it used.

What does it deliberately leave out?

Cosmetic-only changes such as formatting, import reordering, and minor renames. It also avoids inferring intent or motivation, describing changes only functionally.

Does it modify anything?

No. It only reads local git history and writes a text summary; it makes no commits, no writes, and no network calls.

Install what-did-i-get-done

Download and extract the skill files to your .claude/skills/ directory.

Quick Setup:

  1. Copy the skill folder to .claude/skills/
  2. Claude will automatically detect and use the skill

Repository

cursor/plugins