Skip to content
cccskills
FreePublished on GitHub

commit-history

List Git commits linked to agent work sessions, with branch or repository filters. See each commit’s message, date, linked sessions, and observation counts to review recorded changes alongside their session context.

OriginalShow the original 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.

See how to install

Good for

  • Review recent commits linked to agent sessions
  • Filter linked commits by branch
  • Review linked commits for a specific repository
  • Find the sessions associated with a commit

Files included (3)

  • SKILL.md2.1 KB
  • EXAMPLES.md1.5 KB
  • TROUBLESHOOTING.md3.7 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Connect agentmemory to coding agents such as Claude Code and Codex while preserving existing server settings. It guides configuration, host restarts, and checks that memory tools are available and can save and retrieve information.

  • Connecting agentmemory to a coding agent
  • Checking supported agents and connection methods
  • Investigating an incorrect configuration path
rohitg00/agentmemory29.7KUpdated Oct 18, 2026

Explain how agentmemory stores and retrieves coding agents’ memories, including its engine, search methods, memory lifecycle, ports, and web viewer. Useful for understanding the system or planning extensions to its functions.

  • Understand how agent memories are stored and retrieved
  • Plan extensions to agentmemory
  • Check memory capture in the web viewer
rohitg00/agentmemory29.7KUpdated Oct 18, 2026

Set up and troubleshoot a local agentmemory server by checking MCP connections, authentication, ports, and environment settings. Understand which optional memory features require additional configuration, model downloads, or token usage before enabling them.

  • Set up a local agentmemory connection
  • Diagnose MCP connection failures
  • Review authentication and custom ports
rohitg00/agentmemory29.7KUpdated Oct 18, 2026

Understand how agentmemory automatically records tool activity, prompts, and session boundaries through hooks, actions triggered by session events. Use it to check integration setup, investigate missing records, and distinguish capture from optional summaries and context injection.

  • Understanding automatic session recording
  • Investigating missing observations
  • Checking capture and summary settings
rohitg00/agentmemory29.7KUpdated Oct 18, 2026

Helps agents choose the right agentmemory tool through MCP, a protocol for connecting agents to tools. It explains tool roles and points to parameter references for saving, retrieving, organizing, and maintaining stored knowledge.

  • Choosing a tool to save or retrieve knowledge
  • Checking tool names and required parameters
  • Reviewing available memory management operations
rohitg00/agentmemory29.7KUpdated Oct 18, 2026

Guides HTTP integration with the agentmemory server for saving and searching knowledge. It explains authentication, request conventions, and endpoint references, including how to connect systems that do not support MCP, the agent tool connection protocol.

  • Saving and searching knowledge over HTTP
  • Connecting a host that does not support MCP
  • Checking authentication and response conventions
rohitg00/agentmemory29.7KUpdated Oct 18, 2026

See all skills by rohitg00

Report a problem with this skill