Guide · Agent skill
How to use the Agent Commit History agent skill (commit-history)
Updated · written with AI from the project's own documentation and checked against our catalogue data
The commit-history skill is a plugin skill from the agentmemory project that lists recent git commits linked to agent sessions. It is useful if you want to see which commits an AI agent made during its sessions, what it shipped on a branch, and the session context behind each commit. After reading this guide you will know what the skill needs, how to install it, how to ask for commits in plain language, and how to filter the results.
Agent Commit Historyrohitg00/agentmemory · Apache-2.0 Download the skill Quick start
- 1Set up agentmemory. Make sure the agentmemory memory system is running so the memory_commits tool is available.
- 2Download the ZIP. Download the commit-history skill ZIP from this page and unzip it.
- 3Place the folder. Move the unzipped folder into ~/.claude/skills/ for personal use or a project's .claude/skills/ folder for one project.
- 4Or upload in the Claude apps. In the Claude apps, go to Settings → Capabilities → Skills and upload the skill.
- 5Ask in plain language. Request something like "show agent commits" or "what has the agent shipped".
- 6Add filters if needed. Include branch=, repo= or a number such as 5 to narrow the results.
What is an agent skill, and what does commit-history do?
An agent skill is a folder containing a SKILL.md file and optional supporting files. It gives an AI agent instructions for a specific task, and the agent loads it when your request matches the skill's description.
Once installed, the commit-history skill tells the agent to call a memory tool named memory_commits when you ask to see agent commits. The result is a newest-first list of commits. Each entry shows the short commit id, branch, date, message, and the linked agent session with how many observations it contains.
- Shows the short commit id, branch, authored date and commit message
- Shows linked session id(s), with observation counts
- Shows a file count when the tool returns files
- Can be narrowed by branch, repo, or number of entries
What you need before installing
This skill does not read git history directly. It depends on the agentmemory memory system. The memory_commits tool must exist for the skill to work. If the tool is not available, the skill can fall back to the agentmemory REST API at GET /agentmemory/commits, but the agentmemory system must still be running.
The skill does not run scripts and does not use the network on its own. Its listed results come from the memory tool, so commits made outside agent sessions may not appear.
- The agentmemory memory system, providing the memory_commits tool (or the REST endpoint GET /agentmemory/commits as a fallback)
- An agent host that supports skills, such as Claude Code or the Claude apps
How to install the commit-history skill
Download the ZIP for the skill from this page and unzip it. The folder contains EXAMPLES.md, SKILL.md and TROUBLESHOOTING.md. Put the unzipped skill folder in one of these locations:
- Personal skills: ~/.claude/skills/ (available in all your projects)
- Project skills: a project's .claude/skills/ folder (available only in that project)
- Claude apps: upload the skill under Settings → Capabilities → Skills
How to trigger the skill with natural requests
You do not need to type a command. Ask the agent in plain language. The skill's description lists the phrases it matches, such as "show agent commits", "what has the agent shipped" and "list linked commits". You can also ask for commits with their session context.
You can add filters in your request. The skill reads branch=, repo= and limit= values, and treats a bare number as the limit.
- "Show agent commits on main."
- "What has the agent shipped?"
- "List linked commits, limit 5."
- "commit-history 5"
memory_commits { "branch": "main", "limit": 20 }Read the output and handle empty results
The skill renders only the commits the tool returned, newest first. Each line includes the short sha, branch, date, message, and linked session id with its observation count. If the skill returns file counts, they appear too.
An empty result means the filter matched nothing, not that agent work is missing. The skill suggests dropping the branch or repo filter and trying again.
9a1b2c3 main 2026-06-07 "rotate refresh tokens" · session 7f3a9c2 (14 obs)Tips for reliable results
Defaults are no branch filter, no repo filter, a limit of 100, and a maximum of 500. If you use the REST fallback, the skill URL-encodes branch, repo and limit values, so names containing characters like ?, & or # do not break the query.
If the memory_commits tool is not available, see TROUBLESHOOTING.md in the skill folder. It explains how to check your agent host and MCP connection.
- Use branch= to focus on one branch, such as main
- Use a small limit when you only need recent work
- Check TROUBLESHOOTING.md first if the tool is missing
What people use it for
- Reviewing which commits an AI agent made on a feature branch before merging
- Listing what an agent has shipped on main over a recent period
- Checking the session behind a commit, including its observation count
- Scanning a repo's recent agent-linked commits when working across several projects
Frequently asked questions
Is the commit-history skill free to use?
The skill is published under the Apache-2.0 licence. This page does not state pricing for the wider agentmemory project, so check its own documentation for that.
What do I need to install commit-history?
You need the agentmemory memory system so that the memory_commits tool exists, or the REST endpoint GET /agentmemory/commits as a fallback. Then download the ZIP and place it in ~/.claude/skills/ or a project's .claude/skills/ folder.
Does commit-history run scripts or use the network?
According to the skill listing, it runs no scripts and uses no network on its own. It returns results from the memory tool.
Why are some of my commits missing?
The results come from the memory tool, so commits made outside agent sessions may not appear. An empty result also means the filter matched nothing, so try removing the branch or repo filter.
What should I do if the skill says the memory tool is not available?
Check that the agentmemory memory system is running and that the MCP connection is active. TROUBLESHOOTING.md in the skill folder lists the steps to walk through, in order.
How is commit-history different from commit-context and recall?
commit-history lists many recent linked commits. The skill's own see-also notes say commit-context drills into one commit's session, and recall searches the observations behind a linked session.
New agent skills, repos and AI tools — every week
The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.
Our verdict
Use commit-history if you already run agentmemory and want a quick, filtered list of commits made during agent sessions. Skip it if you do not use agentmemory, since the skill depends on its memory_commits tool, or if you need a plain git log of every commit, because it only shows commits linked to agent sessions.
Download the skill