agentleFS
ScinoScino/fstack/skills/what-did-i-get-done/SKILL.md

what-did-i-get-done

Skill13 starsChanged 58 days agoMITView on GitHub

Summarize authored commits over a user-specified time period into a concise update

10 other projects use a version of this, 5 of them edited.

Adopted by

Most recently taken up by

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 9 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:

    Read commits authored by the current git user email within that range.

    line 16
  2. Distinctive:

    Do not infer intent or motivation.

    line 26

“Common” is measured: kept by at least 6 in 10 of the 9 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

Trigger

Need a short, high-signal summary of work completed in a specific time range (for example: yesterday, last 3 days, or last week).

Workflow

  1. Resolve the requested time window into concrete dates.
  2. Read commits authored by the current git user email within that range.
  3. Exclude merge commits and uncommitted changes.
  4. Synthesize the most important shipped changes into a concise status update.
  5. Include the actual date range used in the final summary.

Guardrails

  • Be extremely concise and information-dense.
  • Prioritize substantial behavior or architecture changes.
  • Omit cosmetic-only changes (formatting, imports, minor renames).
  • Do not infer intent or motivation. Describe changes functionally.

Output

  • One short summary suitable for a status update
  • Real date range
  • Optional 2-5 bullets for major changes only

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.