commit-history

어떤 스킬인가요?

에이전트 세션과 연결된 최근 Git 커밋을 나열하며, 필요에 따라 브랜치나 리포지토리로 필터링할 수 있습니다. 사용자가 “에이전트 커밋을 보여줘”, “에이전트가 무엇을 배포했는지”, “연결된 커밋 목록”을 요청하거나, 세션 컨텍스트가 포함된 커밋을 확인하고자 할 때 사용합니다.

설치 방법

프로젝트 폴더에서 아래 명령어를 실행하고, 설치할 에이전트를 선택하세요.

설치 명령을 직접 실행해야 적용됩니다. 지원 에이전트와 필요한 권한·라이선스는 제작자의 안내를 확인하세요.

스킬 원문 파일

# commit-history worked examples

## 1. Branch filter

User: "Show agent commits on main."

Invocation:

```json
memory_commits { "branch": "main", "limit": 100 }
```

Response:

```json
{
  "commits": [
    { "short": "9a1b2c3", "branch": "main", "authoredAt": "2026-06-07T09:12:00Z",
      "message": "rotate refresh tokens", "sessionIds": ["7f3a9c21"],
      "observationCount": 14, "files": 3 },
    { "short": "b21d004", "branch": "main", "authoredAt": "2026-06-05T14:40:00Z",
      "message": "rate limiter audit", "sessionIds": ["b21d004e"],
      "observationCount": 9, "files": 1 }
  ]
}
```

Present:

> - `9a1b2c3` main 2026-06-07 "rotate refresh tokens", session `7f3a9c2` (14 obs, 3 files)
> - `b21d004` main 2026-06-05 "rate limiter audit", session `b21d004` (9 obs, 1 file)

## 2. Bare number as limit

User: "commit-history 5"

Treat `5` as the limit:

```json
memory_commits { "limit": 5 }
```

Render the five newest linked commits in the same format.

## 3. Empty result

User: "Show agent commits on release-2.0."

```json
memory_commits { "branch": "release-2.0", "limit": 100 }
```

Response:

```json
{ "commits": [] }
```

Present:

> No agent-linked commits on `release-2.0`. Drop the branch filter to see all
> linked commits, or try a different branch.

REST fallback for this same call, with encoding:

```http
GET /agentmemory/commits?branch=release-2.0&limit=100
```

Build it with `URLSearchParams` so a branch like `feat/a&b` becomes
`feat%2Fa%26b` rather than breaking the query.

---
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

```json
memory_commits { "branch": "main", "limit": 20 }
```

Expected output:

```text
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](TROUBLESHOOTING.md) if `memory_commits` is not available.

<!-- AUTOGEN:troubleshooting START - generated by scripts/skills/generate.ts, do not edit by hand -->
# Troubleshooting agentmemory skills

Recovery steps for separately installed skills. This document is generated into
each skill directory so native skill readers can open it without parent traversal.

## "MCP tool not available"

Missing tools can mean a stopped MCP process, a disconnected daemon, or an
explicitly reduced tool surface. Walk these in order:

1. Identify the host. In Claude Code, inspect `/plugin list` and `/mcp`.
   In Hermes, inspect the configured memory provider and `mcp_servers` separately.
   In OpenClaw, validate the host configuration and inspect its MCP servers and
   native plugins separately. In Pi or OMP, inspect `/agentmemory-status` and the
   MCP inventory separately; native save/search does not prove the broader tools
   are connected. Do not run another host's setup commands.
2. Restart or reload the affected host connection after configuration changes.
3. Inspect the connected tool inventory. Hermes may namespace MCP tools; invoke
   the actual advertised names and schemas. A native memory provider is not
   proof that every MCP tool or shared skill is available.
4. Check `agentmemory status` and the daemon's `AGENTMEMORY_TOOLS` setting.
   Codex's bundled bridge lists the daemon's enabled tools. The standalone shim
   used by other hosts can fall back to seven basic tools with a separate store.
   Do not claim full daemon functionality based on those seven tools.
5. If `agentmemory connect codex` and the Codex plugin are both enabled, choose
   one MCP connection. Check `/hooks` before adding global hook fallbacks.

Hermes, OpenClaw, Pi and OMP connector installations bundle skills; other hosts
may install them separately. Check the host's skill inventory and open this file
from the installed skill directory. Test automatic capture with a real turn and
a recorded observation; tool connectivity alone does not establish lifecycle
capture.

An outage or timeout is not an empty search result. Report the failure. A write
may have committed before the response was lost; inspect state before retrying.

## REST fallback

When the MCP tools stay unavailable but the daemon is running, call the REST
API directly:

1. Set `AGENTMEMORY_URL` to the daemon base URL (default `http://localhost:3111`).
2. The REST API requires a bearer credential by default. Use the host's explicit
   `AGENTMEMORY_SECRET`; for loopback URLs only, fall back to the secret in
   `~/.agentmemory/.env` and then `~/.agentmemory/secret`. Load the value locally
   without displaying it. Never send a local-file secret to a remote URL.
   If `AGENTMEMORY_CREDENTIAL_MODE=explicit`, require the explicit host credential
   and do not read local credential files.
   Authenticated REST fallback requests require HTTPS for non-loopback
   URLs; HTTP is allowed for loopback URLs (`localhost`, `127.0.0.0/8`, or `[::1]`).
   Reject redirects on authenticated requests. Do not print or save the secret.

Endpoint map by skill:

| Skill           | REST call                                                        |
| --------------- | --------------------------------------------------------------- |
| remember        | `POST /agentmemory/remember`                                     |
| recall          | `POST /agentmemory/smart-search`                                 |
| recap           | `GET /agentmemory/sessions` + `POST /agentmemory/smart-search`   |
| handoff         | `GET /agentmemory/sessions` + `POST /agentmemory/smart-search`   |
| session-history | `GET /agentmemory/sessions`                                      |
| commit-context  | `GET /agentmemory/session/by-commit?sha=<sha>`                   |
| commit-history  | `GET /agentmemory/commits` (URL-encode every query param)       |

The MCP host reads the plugin MCP configuration. Restart the daemon after
changing its configuration, then restart or reconnect the host MCP process after
changing its URL or explicit secret. The local bridge reads the credential files
for each request; it does not inherit other daemon `.env` settings.
<!-- AUTOGEN:troubleshooting END -->