mcpField
W
what-did-i-get-done

what-did-i-get-done

github.com/michael-denyerProductivity3.6k806 installsUpdated today
Repository

About what-did-i-get-done

A skill that summarizes work completed by the current Git user over a requested date range. It filters commits and produces a concise status update with the dates covered.

Key features

  1. 01Resolve requested dates
  2. 02Read commits by current Git user
  3. 03Exclude merge commits and uncommitted changes
  4. 04Prioritize substantial changes
  5. 05Include the date range

Use cases

  1. 01Preparing a daily or weekly status update
  2. 02Summarizing shipped work over a chosen period
  3. 03Reviewing completed changes without cosmetic noise

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/michael-denyer/pstack-claude --skill what-did-i-get-done

After installing, type/what-did-i-get-donein Claude Code to confirm it loaded.

Details

From the project README

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

Comments

Markdown supported