michael-denyer/pstack-claude

what-did-i-get-done

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

Quelltext ansehen

Verwendung

  1. Installationsbefehl kopieren und das Quellpaket vor der Installation in der eigenen Agentenumgebung prüfen.
  2. Benötigte Werkzeuge, Zugangsdaten und Hosts im Original prüfen.
  3. Eingabe und gewünschtes Ergebnis beschreiben und die Ausgabe mit den Quellen abgleichen.
npx skills add https://github.com/michael-denyer/pstack-claude --skill what-did-i-get-done

Vor dem Start

  • Die Installation umfasst weder Modellabo noch API-Kontingent oder Dateizugriffsrechte.
  • Sterne und Installationen zeigen Aktivität, keine unabhängige Qualitäts- oder Sicherheitsprüfung.
Originales Skill-Dokument

Aus dem Quell-Repository gerendert; Überschriften, Beispiele, Code, Tabellen, Links und Bilder bleiben erhalten.

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

Verwandte Aufgaben

aus demselben Repository

Weitere Skills

Alle Skills
michael-denyer
Community

architect

Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in. Use for /architect, 'architect this', 'design this', or non-trivial work where jumping to code would lock in the wrong shape.

Installationen / 1h
1
GitHub Stars
3969
Aktualisiert
4. Nov.
michael-denyer
Community

babysit

Watch an open PR — fix failing CI, handle the straightforward review comments, and drive it to a mergeable state. Claude Code analog of Cursor's built-in /babysit. Use after opening a PR when the user wants the agent to shepherd it without re-prompting.

Installationen / 1h
1
GitHub Stars
3969
Aktualisiert
4. Nov.
michael-denyer
Community

benchmark-checklist

Vet a perf measurement (limiter, tuning, limits, errors, repeatability, relevance, and whether the work happened) before you report or act on it. Use when you run a benchmark or report a speedup or regression you measured.

Installationen / 1h
1
GitHub Stars
3969
Aktualisiert
4. Nov.
michael-denyer
Community

blast-radius

Find what a change could break somewhere else before it ships, beyond the diff, and prove the one fact it's safe because of by running real code instead of writing it up. Use for 'blast radius of X', 'what could this break', reviewing a small diff you don't trust, or a brief that asserts something about existing code ('make X public', 'X already handles Y') before you design against that assertion.

Installationen / 1h
1
GitHub Stars
3969
Aktualisiert
4. Nov.