skills.rest
bnferguson
bnfergusonCOMMUNITY
Explore all skills by this author →
GitHub

what-did-i-get-done

Summarizes authored git commits over a specified time range into a concise status update.

Updated Nov 10, 2013
Search Tags:#git#productivity#git history#status update#standup#commit summary#work recap
One-click install
npx skills add https://github.com/bnferguson/dotfiles --skill what-did-i-get-done-bnferguson
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: what-did-i-get-done
Source: https://github.com/bnferguson/dotfiles/tree/main/.agents/skills/what-did-i-get-done
Command: npx skills add https://github.com/bnferguson/dotfiles --skill what-did-i-get-done-bnferguson

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Recalling what you actually shipped over the past days or weeks is tedious when writing standup updates, status reports, or weekly recaps. This Skill reads your git history and turns it into a short, high-signal summary. ## Core Features & Use Cases - Time-Range Commit Analysis: Resolves natural-language periods like "yesterday" or "last 3 days" into concrete dates and reads commits authored by your git email. - Noise Filtering: Excludes merge commits, uncommitted changes, and cosmetic-only edits such as formatting or renames. - Use Case: Before a Monday standup, ask for a summary of last week's work and receive a concise update with the real date range and 2-5 bullets covering only substantial behavior or architecture changes. ## Quick Start Ask the assistant to summarize what you got done last week from your git commits.

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 my git commits for a standup update?▼

Specify a time range such as yesterday, last 3 days, or last week, and the Skill reads commits authored by your git user email in that window. It produces one short summary with the real date range and optional bullets for major changes.

How to generate a weekly work report from git history?▼

Request a summary for the desired week and the Skill resolves it into concrete dates, filters your authored commits, and synthesizes the most important shipped changes. Merge commits and uncommitted changes are excluded automatically.

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

No, merge commits and uncommitted changes are explicitly excluded. Cosmetic-only changes like formatting, import reordering, and minor renames are also omitted from the output.

Which commits are included in the summary?▼

Only commits authored by the current git user email within the resolved date range are included. The Skill prioritizes substantial behavior or architecture changes over minor edits.

What are the limitations of summarizing work from git commits?▼

The summary describes changes functionally and does not infer intent or motivation. Work not captured in commits, such as meetings, reviews, or uncommitted experiments, will not appear in the output.

Related Skills

Explore More Software Engineering Skills→
MartinStykMartinStyk
343

git-commit-author

Enforce human-only authorship in git commits by blocking AI-generated trailers.

Community
Basic
cafe3310cafe3310
248

weekly-report-writer

Generate structured weekly progress reports from Obsidian Markdown notes.

Community
Intermediate
The-Vibe-CompanyThe-Vibe-Company
2.4k

code-review

Review a git diff against coding standards and the originating spec using parallel sub-agents.

Official
Intermediate
darellchua2darellchua2
4

jira-git-workflow

Create JIRA tickets, Git branches, and PLAN.md files.

Community
Intermediate