what-did-i-get-done

Summarize authored git commits within a specified date range into a status update.

Updated May 18, 2025
One-click install
npx skills add https://github.com/nthpaul/dotfiles --skill what-did-i-get-done-nthpaul
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: what-did-i-get-done
Source: https://github.com/nthpaul/dotfiles/tree/main/cursor/.cursor/plugins/cache/cursor-public/cursor-team-kit/d1cdb88a9eb33cf392395c87e3fd76419fc1010e/skills/what-did-i-get-done
Command: npx skills add https://github.com/nthpaul/dotfiles --skill what-did-i-get-done-nthpaul

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you quickly produce a high-signal summary of work you shipped during a specific time window, without manually reading and filtering commits.

Core Features & Use Cases

  • Time-range commit summarization: Resolves a user-requested window into concrete dates and reads commits authored by your git user within that range.
  • Noise reduction: Excludes merge commits and focuses on meaningful shipped changes rather than cosmetic edits.
  • Status-update output: Produces a concise update that includes the actual date range and optionally highlights 2–5 major changes only.

Quick Start

Ask for a summary of your authored commits for the last 3 days, and include the exact date range used plus an optional short list of only the biggest changes.

Frequently Asked Questions about what-did-i-get-done

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a weekly status update from my git commits?

To create a status update from git commits, specify a time period like the last 3 days. The summarizer resolves this into exact dates, reads your authored commits, excludes merge commits, and synthesizes functional changes into a concise progress update including the date range.

Can I filter out merge commits when summarizing my engineering progress?

Yes, merge commits are automatically excluded when generating a progress update. The summarization process filters out merge commits and irrelevant noise, focusing solely on meaningful shipped changes to produce a high-signal work update for teams or stakeholders.

What is the best way to report engineering productivity from git history for stakeholders?

The best way to report engineering productivity is to summarize git commits by author email over a specific time range. This produces a concise status update highlighting major functional changes, giving stakeholders a clear view of shipped work without manual commit filtering.

Does the git commit summarizer require a specific author email to generate a progress report?

Yes, the git commit summarizer requires an author email to generate a progress report. It selects commits by matching your git user email within the specified time window to ensure the status update reflects your individual authored contributions.

How do I limit the status update to only show the biggest changes from my commit history?

Limit the status update to the biggest changes by requesting an optional short list of major updates. The summarizer synthesizes functional shipped changes and can optionally highlight only 2 to 5 major changes from your commit history within the computed date range.

What limitations should I expect when turning recent commits into a concise work update?

Limitations include relying strictly on git commit history and author email matching, meaning uncommitted work or non-code tasks are excluded. It also focuses on functional changes, automatically discarding merge commits and irrelevant noise to ensure a concise output.