What Did I Get Done

Summarize authored work from the record, not from memory.

Workflow

Establish identity and window: which author(s) and what period (default: the last 7 days; take the user's override).
Collect: git log --author=<you> --since=<window> --stat across the repos in play; include merged PRs via gh pr list --author <you> --state merged --search "merged:>=<window-start>" --limit 500 where the user cares about review surface (--state defaults to open, so it must be named; --author needs its value; the default limit of 30 silently truncates a busy window — pass an explicit limit or paginate until a page comes back short).
Group by theme, not by commit: a theme line names the outcome ("auth retry hardening"), the commits underneath are the evidence.
Count honestly: commits, net lines, tests added. Mechanical churn (renames, lockfiles) is grouped separately or left out, never passed off as progress.
Started-but-unfinished: branches and PRs opened but not landed in the window, each with what remains — the section standups actually need.

Rules

Every theme line links its commit range; no theme without commits.
No inflating: a revert-pair counts as zero, and that is said, not hidden.
The summary is prose over a small table; it fits in one screen.

Files1

1 files · 1.0 KB

Select a file to preview

Overall Score

72/100

Grade

B

Good

Grades are signals, not a certification. Always review a skill yourself before use.

Safety

82

Quality

68

Clarity

75

Completeness

58

Summary

This skill guides an AI agent to generate work summaries from git history and merged pull requests, grouped by theme with commit evidence. It analyzes authored work over a configurable time window (default 7 days), separates mechanical churn, and identifies unfinished branches for standups and status reports.

Detected Capabilities

git log query executionGitHub CLI integration (gh pr list)repository analysiscommit history parsingdata aggregation and grouping

Trigger Keywords

Phrases that agents use to match this skill to user intent.

standup summarywhat did i buildweekly work reviewcommit range summarypr merged trackingweek in reviewwork progress report

Risk Signals

INFO

GitHub CLI usage (gh pr list) requires authentication context; no explicit handling of auth failures or rate limits documented

Workflow step 2

INFO

Default GitHub CLI pr list limit of 30 items silently truncates output; skill correctly identifies this and recommends explicit limit or pagination

Workflow step 2

Referenced Domains

External domains referenced in skill content, detected by static analysis.

github.com

Use Cases

Generate standup summaries from committed work
Create weekly 'what did I get done' reports
Aggregate work across multiple repositories by theme
Track progress on multiple parallel projects
Review completed and in-progress work for performance discussions

Quality Notes

Excellent clarity on core principles: 'count honestly', separate mechanical churn, link commit ranges to evidence
Workflow is concrete and actionable with specific command examples (git log --author, gh pr list flags)
Clear statement of what should NOT happen (no inflating, reverting pairs count as zero)
Identifies a common pitfall: silent truncation at default limit of 30 PRs — shows domain awareness
Missing: concrete examples of theme grouping (what does 'auth retry hardening' look like as structured output?)
Missing: handling for edge cases (empty commit window, no merged PRs, private repos, auth failures)
Missing: output format specification (prose + table structure not fully defined)
Missing: how to handle commits from co-authors or merge commits
Missing: guidance on dealing with rebased histories that obscure authorship

Model: claude-haiku-4-5-20251001Analyzed: Nov 8, 2026

Reviews

Add this skill to your library to leave a review.

No reviews yet

Be the first to share your experience.

what-did-i-get-done