what-did-i-get-done

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

1|Updated Sep 18, 2015

Search Tags:#automation #git #commit #developer-tools #summary #time-window #status-update

Ready to run

npx skills add https://github.com/martindzejky/dotfiles --skill what-did-i-get-done

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: what-did-i-get-done
Source: https://github.com/martindzejky/dotfiles/tree/main/ai/skills/what-did-i-get-done
Command: npx skills add https://github.com/martindzejky/dotfiles --skill what-did-i-get-done

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers create a compact status update by summarizing commits authored within a user-specified time window, reducing the need to manually comb through history.

Core Features & Use Cases

Resolve the requested time window into concrete dates.
Read commits authored by the current git user 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.

Quick Start

Summarize commits for a chosen time window, for example yesterday or last week.

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 summarize git commits into a status update for a specific time window?▼

To summarize git commits into a status update, specify a time period like yesterday or last week. The tool reads commits authored by the current git user within that range, excludes merges, and synthesizes the most important shipped changes into a concise summary.

What is the best way to generate a developer status update from recent commit history?▼

Generating a developer status update from recent commit history involves resolving a requested time window into concrete dates and reading your authored commits. It automatically excludes uncommitted changes and merge commits to highlight only your shipped changes.

Does the commit summary include merge commits and uncommitted changes?▼

No, the commit summary explicitly excludes merge commits and uncommitted changes. It only reads commits authored by the current git user within the specified time range to ensure the status update reflects your actual individual contributions.

Can I use a natural language time window like last week to filter my git activity?▼

Yes, you can use a natural language time window like last week to filter your git activity. The process resolves the requested time window into concrete dates and includes the actual date range used in the final summary output.

How do I create a concise summary of shipped changes without manually combing through git log?▼

To create a concise summary of shipped changes without manually combing through git log, automate the process by reading your authored commits over a chosen period. The tool synthesizes the most important changes into a compact status update.

What limitations should I expect when summarizing commits over a custom date range?▼

When summarizing commits over a custom date range, expect the limitation that only commits authored by the current git user are included. Merge commits and uncommitted changes are omitted, meaning the summary focuses strictly on individual shipped changes.