SkillHub

Skills rohitg00 agentmemory agentmemory

commit-history

Use it when:
You want to see what the agent has shipped: commits alongside the sessions that produced them.
It does:
Lists the git commits linked to agent sessions in agentmemory, filtered by branch or repo if you ask, up to 100 by default and 500 at most.
You get:
Newest first: short sha, branch, date, first line of the message, linked session ids with observation counts, and file counts.
Needs:
agentmemory's memory server running, with its MCP tools connected to your agent.
Unlike commit-context:
That one traces one piece of code to its session; this one lists many commits.

Skill 7 of 8 in the agentmemory bundle, after recap and before commit-context.

TL;DR

Part of agentmemory, a memory server that records what coding agents do in each session as observations. commit-history lists the git commits linked to those sessions. You can filter by branch and by repository URL or a fragment of it, and set a limit; a bare number is the limit, and by default there's no filter and up to 100 commits, capped at 500. The list shows only what the tool returned, newest first, with the short sha, branch, authored time, first line of the message, the linked sessions' short ids with their observation counts, and the number of files when given. An empty result means the filter matched nothing, and the agent suggests dropping the branch or repo filter. When the MCP tools are missing and it calls agentmemory's REST API instead, it URL-encodes every filter value.

Summarizes the skill at f0f7378.

npx skills add https://github.com/rohitg00/agentmemory --skill commit-history

skills.sh pageSource on GitHubAll skills from rohitg00/agentmemory

Total Downloads
14,200 on skills.sh, Nov 9, 2026
Repo stars
30,216 rohitg00/agentmemory
First seen
May 18, 2026 on skills.sh
Weekly Downloads
256
-35% over the 8 weeks to Nov 9
Weekly values
Week toInstalls
Sep 21394
Sep 28373
Oct 5341
Oct 12312
Oct 19331
Oct 26315
Nov 2295
Nov 9256
Category
category:agentscategory:engineeringcategory:software-engineering

Build agents, orchestrate workers and give agents memory.

Test-first work, implementation from specs, git hygiene and scope control.

Everything for building software: planning, coding, debugging, design, frameworks, cloud, agents and skills.
Type
type:tool

Operates a CLI, API, app or bundled script to get something done.
Effect
effect:none

Adds no side effects of its own. It shapes how the agent thinks, writes or reviews. Guidelines and routers are always effect:none, even when the task they support edits code.
Needs
needs:mcp

Needs an MCP server connected.
Publisher
by:official

A verified publisher on skills.sh, or the company or maintainer behind the product the skill operates.
Topics
memorygit
Stack
stack:agentmemorystack:git

SKILL.md

From rohitg00/agentmemory at f0f7378. Checked daily, last changed Nov 6, 2026.

Frontmatter
name: commit-history
description: 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.
argument-hint: "[branch=... repo=... limit=...]"
user-invocable: true

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

  1. 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.
  2. Call memory_commits with the parsed filters.
  3. 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.
  4. 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.