agentleFS
Yeachan-HeoYeachan-Heo/oh-my-claudecode/skills/what-did-i-get-done/SKILL.md

what-did-i-get-done

Skill41k starsChanged 7 days agoMITView on GitHub

Summarize authored commits over a period, grouped by theme with commit-range evidence, mechanical churn separated, and unfinished branches named. For standups and 'what did I get done'.

10 other projects use a version of this.

Adopted by

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projectsWeek of Nov 8: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Most recently taken up by

Who's talking about Yeachan-Heo/oh-my-claudecode

The biggest 5 of 81 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 81

Talked about on GitHub, YouTube, Bluesky and the web (81 times).

On GitHub · 50

45 more on GitHub

On YouTube · 20

15 more on YouTube

On Bluesky · 10

5 more on Bluesky

On the web · 1

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 8 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every theme line links its commit range.

    line 40
  2. Distinctive:

    No inflating: a revert-pair counts as zero, and that is said, not hidden.

    line 41

“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

What Did I Get Done

Summarize authored work from the record, not from memory.

Workflow

  1. Establish identity and window: which author(s) and what period (default: the last 7 days; take the user's override).
  2. 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).
  3. Group by theme, not by commit: a theme line names the outcome ("auth retry hardening"), the commits underneath are the evidence.
  4. Count honestly: commits, net lines, tests added. Mechanical churn (renames, lockfiles) is grouped separately or left out, never passed off as progress.
  5. 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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.