Commit History

When you need to see what commits an AI agent has actually shipped, this pulls the git history with session context attached. You get short SHAs, branch names, timestamps, and the observation count from each linked session, newest first. Filter by branch, repo, or limit the results. The real win is tying commits back to the agent sessions that produced them, so you can trace from "what shipped" to "what the agent saw and did." Empty results mean your filter matched nothing, not that the agent hasn't been working. Pairs well with commit-context if you need to drill into a specific commit's full session data.

skills.sh installs: 14.3K
GitHub stars: 30.2K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add rohitg00/agentmemory --skill commit-history --agent claude-code

Installs into .claude/skills of the current project.

Files

The user wants a list of agent-linked commits. Filter args: $ARGUMENTS

Quick start

memory_commits { "branch": "main", "limit": 20 }

Expected output:

9a1b2c3 main 2026-06-07 "rotate refresh tokens" · session 7f3a9c2 (14 obs)
b21d004 main 2026-06-05 "rate limiter audit"    · session b21d004 (9 obs)

Why

Render only the commits the tool returned, newest first. An empty result means the filter matched nothing, not that work is missing.

Workflow

Parse $ARGUMENTS for branch=<name>, repo=<url-or-fragment>, limit=<n>. A bare numeric token is the limit. Defaults: no branch, no repo, limit 100, max 500.
Call memory_commits with the parsed filters.
Render reverse-chronologically: short sha, branch, authored timestamp, first line of the message, linked session id(s) (first 8) with observation counts, and file count when files is present.
Empty result: tell the user the filter matched nothing and suggest dropping the branch or repo filter.