what-did-i-get-done

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.

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.

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.

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.

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.

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.