commit-history
List recent git commits linked to agent sessions, optionally filtered by branch or repo. Use when the user asks "show agent commits", "what has the agent shipped", "list linked commits", or wants commits with their session context.
- Installs
- 13.8K
- Last 24h
- +51
- Trending rank
- #3306
- Security
- Pass
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/rohitg00/agentmemory --skill commit-history- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads commit-history automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
Security audits
Independent scans of the skill's instructions and bundled files.
SKILL.md
The instructions your agent reads when the skill is triggered.
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
$ARGUMENTSforbranch=<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_commitswith 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
filesis present. - Empty result: tell the user the filter matched nothing and suggest dropping the branch or repo filter.
Anti-patterns
WRONG (REST fallback): concatenate ?branch= + raw branch name, so a name with
?, &, or # corrupts the query string.
RIGHT: URL-encode every value with URLSearchParams/encodeURIComponent before
appending to GET /agentmemory/commits.
Checklist
- Filters parsed; bare number treated as limit; limit capped at 500.
- Output is reverse-chronological.
- Session ids and observation counts come straight from the response.
- REST fallback URL-encodes branch, repo, and limit.
See also
commit-context: drill into one commit's session.recall: search the observations behind a linked session.
Troubleshooting
See TROUBLESHOOTING.md if memory_commits is not available.
FAQ
What does the commit-history skill do?
List recent git commits linked to agent sessions, optionally filtered by branch or repo. Use when the user asks "show agent commits", "what has the agent shipped", "list linked commits", or wants commits with their session context.
How do I install commit-history?
Run npx skills add https://github.com/rohitg00/agentmemory --skill commit-history in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/commit-history/ (personal) or .claude/skills/commit-history/ (project).
Which AI agents can use commit-history?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is commit-history safe to install?
Security partners have reviewed it: Gen Agent Trust Hub passed; Socket passed; Snyk passed. As with any skill, read the SKILL.md and bundled scripts before installing.
Who maintains commit-history?
It is published by rohitg00 in rohitg00/agentmemory. It has 13,753 recorded installs.
More from rohitg00/agentmemory
remember
rohitg00/agentmemory
Save an insight, decision, or learning to agentmemory's long-term storage with searchable concept tags. Use when the user says "remember this", "save this", "note that", "don't forget", or wants to preserve knowledge for future sessions.
recall
rohitg00/agentmemory
Search agentmemory for past observations, sessions, and learnings about a topic using hybrid BM25 plus vector plus graph search. Use when the user says "recall", "what did we do about", "did we ever", "have we seen", or needs context from past sessions.
session-history
rohitg00/agentmemory
Show what happened in recent past sessions on this project as a clean timeline. Use when the user asks "what did we do last time", "session history", "past sessions", or wants an overview of previous work.
forget
rohitg00/agentmemory
Delete selected durable memories from agentmemory after showing them and getting explicit confirmation. Use when the user says "forget this", "delete memory", "remove that note", or wants to scrub specific data for privacy.
recap
rohitg00/agentmemory
Summarize the last N agent sessions for the current project, grouped by date, with highlight observations per session. Use when the user asks "recap", "what have we been doing", "today", "this week", or wants a rollup of recent work.
commit-context
rohitg00/agentmemory
Trace a file, function, or line back to the agent session that produced its current commit. Use when the user asks "why is this code here", "what was the agent doing when this changed", "who wrote this", or wants context on a specific location in the codebase.
Popular code quality & workflow skills
grill-me
mattpocock/skills
A relentless interview to sharpen a plan or design.
improve-codebase-architecture
mattpocock/skills
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
handoff
mattpocock/skills
Compact the current conversation into a handoff document for another agent to pick up.
domain-modeling
mattpocock/skills
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
codebase-design
mattpocock/skills
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.