commit-history
This skill lists recent Git commits linked to agent sessions, with optional filtering by branch or repository. It enables developers to quickly understand what code changes an AI agent has made within specific sessions, providing crucial development context. This enhances project management and collaboration by offering clear traceability of agent-driven code modifications, ensuring teams can easily track and review the agent's contributions to the codebase.
npx skills add https://github.com/rohitg00/agentmemory --skill commit-historyBefore / After Comparison
1 组Before this skill, developers had to manually sift through Git logs or attempt to correlate agent actions with code commits, a process that was time-consuming and prone to errors. This made it difficult to accurately track the agent's code contributions and project progress.
With this skill, developers can quickly list Git commits linked to specific agent sessions, with precise filtering by branch or repository. This significantly streamlines code review and project tracking, ensuring transparency and traceability of the agent's work.
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
- Parse
$ARGUMENTSforbranch=<name>,repo=<url-or-fragment>,limit=<n>. A bare numeric token is the limit. Defaults: no branch, no repo, limit 100, max 500. - Call
memory_commitswith the parsed filters. - 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
filesis present. - 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 ../_shared/TROUBLESHOOTING.md if memory_commits is not available.
User Reviews (0)
Write a Review
No reviews yet
Statistics
User Rating
Rate this Skill