菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| 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
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)
Render only the commits the tool returned, newest first. An empty result means the filter matched nothing, not that work is missing.
$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.memory_commits with the parsed filters.files is present.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.
commit-context: drill into one commit's session.recall: search the observations behind a linked session.See ../_shared/TROUBLESHOOTING.md if memory_commits is not available.
How agentmemory wires into host coding agents via the connect command. Use when installing agentmemory into a specific agent, when asked which agents are supported, or when a connect adapter writes the wrong config path.
How agentmemory is built, the iii engine primitives it runs on, its storage model, ports, and the viewer. Use when reasoning about how memory is stored or retrieved end to end, when extending the system, or when answering how agentmemory works under the hood.
agentmemory configuration, environment variables, ports, and feature flags. Use when enabling a feature, changing ports, setting an API key, configuring auth, or explaining why a feature is off by default.
The agentmemory plugin hooks that capture observations automatically across the agent session lifecycle. Use when explaining how memory gets captured without manual saves, when debugging missing observations, or when tuning what gets recorded.
Map of every agentmemory MCP tool, what each does, and its parameters. Use when choosing which memory tool to call, when a tool name or argument is unclear, or when answering what agentmemory can do via MCP.
The agentmemory HTTP REST API surface, the primary protocol for talking to the memory server. Use when calling agentmemory over HTTP, when MCP is unavailable and you need a fallback, or when integrating a host that does not speak MCP.