Skip to content
Back to skills

What Did I Get Done

ASecurity

Use when a user asks what was completed in a named date or commit range. Reads git log and returns a concise dated status report. Don''t use for tasks that require source or remote-system changes.

  • 52 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 3, 2026
ai-agentsgit

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned September 3, 2026

npx -y skills add OutlineDriven/outline-driven-development --skill what-did-i-get-done --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of What Did I Get Done?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for What Did I Get Done
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/outlinedriven-what-did-i-get-done-outline-driven-development/badge)](https://www.skillsdirectory.com/skills/outlinedriven-what-did-i-get-done-outline-driven-development)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: what-did-i-get-done
description: 'Use when a user asks what was completed in a named date or commit range. Reads git log and returns a concise dated status report. Don''t use for tasks that require source or remote-system changes.'
---

# What did I get done

## Contract

| Field | Bound contract |
|---|---|
| Trigger | User explicitly asks to summarize completed work in a named range |
| Authority | Read-only: read git log only; no file write, credential use, remote mutation, or deployment change |
| Side effect | Chat output only; no file, VCS, credential, paid, published, or remote mutation |
| Done | Concise dated status update returned as chat text |

## Inputs

- Range identifier (required): a date range, commit range, branch name, or label the user specifies.
- Session git root (derived): `git -C <session_cwd> rev-parse --show-toplevel` to locate the repo root. Required; abort if git is not inside a repository.
- All other inputs are derived from the range and repo root.

## Procedure

1. Locate the repository root using `git -C <session_cwd> rev-parse --show-toplevel`. Done when: repo root is located, or the step has aborted with "Not a git repository."
2. Run `git -C <repo_root> log --oneline --date=short --format="%h %ad %s" <range>` where `<range>` is the user's range identifier. If the range is empty or unrecognized by git, report the empty result and stop. Done when: commit log is produced or empty result is reported.
3. Run `git -C <repo_root> shortlog -sne <range>` to capture author and commit counts. Omit if the command fails. Done when: author counts are captured or omitted on failure.
4. Produce a concise status report that includes: the date or range label, the number of commits, each commit on its own line as `<short-hash> <date> <subject>`, and author counts from shortlog if available. Done when: status report is produced.
5. Return the report as chat text only. Do not write any file. Done when: report is returned as chat text.

## Failure and recovery
| Failure class | Result |
|---|---|
| Not a git repository | Abort: report "Not a git repository." |
| Git range not recognized | Report empty result for that range; stop. |
| Git command fails | Abort: report the git error verbatim. |
| No commits in range | Report "No commits found in range." |

Partial-result rule: if some steps succeed, return what was gathered; stop on the first failure. Rollback: none needed. No mutation occurs.

## Output
Chat text containing a concise dated status update: the range label, commit count, per-commit lines (`<hash> <date> <subject>`), and author summary if available.

Files in this skill

  • SKILL.md2.6 KB
  • agents/openai.yaml145 B

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…