mcpField
W
what-did-i-get-done

what-did-i-get-done

github.com/cursorProductivity14.5k2.5k installsUpdated today
Repository

About what-did-i-get-done

What did I get done is a skill that turns authored Git commits from a requested time range into a concise work update. It filters out merge commits and uncommitted changes, prioritizing substantial changes and stating the dates used.

Key features

  1. 01Resolve requested ranges into dates
  2. 02Read commits by the current Git user
  3. 03Exclude merges and uncommitted changes
  4. 04Summarize substantial changes concisely
  5. 05Include the date range in the update

Use cases

  1. 01Prepare a daily work status
  2. 02Summarize changes from the past few days
  3. 03Draft a weekly progress update

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/cursor/plugins --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