Commit Context
- 9k installs
- 26.6k repo stars
- Updated August 3, 2026
- rohitg00/agentmemory
Traces file/function/line to originating agent session via git SHA and memory lookup
About
This skill connects code locations to their originating agent sessions by combining git blame/log with session memory lookups. Developers invoke it when they need to understand why specific code exists, what the agent was doing during that commit, or who authored a change. The workflow uses git blame for line ranges, git log for functions or files, then queries memory_commit_lookup with the SHA to retrieve linked session details including observations, summaries, and timestamps. When commits predate session linking (commit: null), it reports that fact without inventing context.
- Uses git blame/log to find commit SHAs for specific files, functions, or line ranges
- Queries memory_commit_lookup with SHA to retrieve linked agent session metadata
- Returns commit details (sha, branch, author, message) plus session info (id, observation count, summary)
- Handles pre-linked commits by reporting 'predates session linking' when lookup returns null
- Surfaces importance >=7 observations from linked sessions via memory_recall
Commit Context by the numbers
- 9,014 all-time installs (skills.sh)
- +659 installs in the week ending Aug 5, 2026 (Skillselion tracking)
- Ranked #13 of 733 Git & Pull Requests skills by installs in the Skillselion catalog
- Security screen: HIGH risk (skills.sh audit)
- Data as of Aug 5, 2026 (Skillselion catalog sync)
commit-context capabilities & compatibility
- Capabilities
- git blame execution · git log parsing · sha extraction · memory commit lookup · session metadata retrieval · observation recall · null handling
- Works with
- github · gitlab · bitbucket
- Use cases
- code review · debugging · documentation · research
- Platforms
- macOS · Windows · Linux · WSL
- Runs
- Runs locally
- Pricing
- Free
npx skills add https://github.com/rohitg00/agentmemory --skill commit-contextAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 9k |
|---|---|
| repo stars | ★ 26.6k |
| Security audit | 1 / 3 scanners passed |
| Last updated | August 3, 2026 |
| Repository | rohitg00/agentmemory ↗ |
What it does
Trace any file, function, or line back to the agent session that created its current commit to understand why code exists.
Who is it for?
Understanding code provenance, debugging agent-generated changes, auditing what sessions produced specific code
Skip if: Tracking human-authored commits, commits predating agent session linking, real-time code generation monitoring
When should I use this skill?
User asks 'why is this code here', 'what was the agent doing', 'who wrote this', or needs context on a codebase location
What you get
Retrieve commit metadata and linked agent session details including observations and context
- commit SHA and metadata
- linked session details
- observation summaries
By the numbers
- Surfaces observations with importance >=7 from linked sessions
- Queries single commit SHA per invocation
Files
The user wants commit context for: $ARGUMENTS
Quick start
git blame -L 40,52 src/auth/refresh.ts # -> SHA 9a1b2c3dmemory_commit_lookup { "sha": "9a1b2c3d4e5f60718293a4b5c6d7e8f901234567" }Expected output:
9a1b2c3 on main by dev: "rotate refresh tokens"
Linked session 7f3a9c2 "Auth refresh rework", 14 obs.Why
Report only what git and the lookup return. When the lookup gives commit: null, the commit predates session linking; do not invent intent.
Workflow
1. Find the SHA: git blame -L <start>,<end> <file> for a line range; git log -L :<function>:<file> for a function; git log -n 1 -- <file> for a bare path. 2. Look it up: memory_commit_lookup { "sha": "<full-sha>" }. 3. Present the commit (sha, short sha, branch, author, message), the linked session(s) (id, project, started/ended, observation count, summary), and the importance >= 7 observations via memory_recall when available.
Anti-patterns
WRONG: lookup returns { "commit": null }, you narrate "the agent was refactoring auth" from the diff alone.
RIGHT: "This commit predates session linking, so there is no recorded agent session. From git show: it changed token rotation in refresh.ts."
Checklist
- SHA came from git blame/log, not a guess.
commit: nullreported as "predates linking", no fabricated session.- Session details quote the lookup response verbatim.
- No intent claimed beyond what observations state.
See also
commit-history: list many agent-linked commits at once.recall: dig deeper into the linked session's observations.
Troubleshooting
See ../_shared/TROUBLESHOOTING.md if memory_commit_lookup is not available.
commit-context worked examples
1. Line range with a linked session
User: "Why is this retry loop here?" (pointing at lines 40-52 of refresh.ts)
Find the SHA:
git blame -L 40,52 src/auth/refresh.ts
# 9a1b2c3d (dev 2026-06-07) ... retry on revoked tokenLook it up:
memory_commit_lookup { "sha": "9a1b2c3d4e5f60718293a4b5c6d7e8f901234567" }Response:
{
"commit": { "sha": "9a1b2c3d...", "short": "9a1b2c3", "branch": "main",
"author": "dev", "message": "rotate refresh tokens" },
"sessions": [ { "id": "7f3a9c21", "project": "app", "observationCount": 14,
"summary": "Reworked refresh rotation" } ]
}Present:
9a1b2c3onmainby dev: "rotate refresh tokens". Linked to session
7f3a9c2 "Auth refresh rework" (14 obs). The retry loop handles a tokenrevoked mid-flight, per the session's high-importance observations.
2. Function lookup, commit predates linking
User: "What was the agent doing when it wrote validateScope?"
git log -L :validateScope:src/auth/scope.ts -n 1
# 1122aabb ...memory_commit_lookup { "sha": "1122aabbccddeeff00112233445566778899aabb" }Response:
{ "commit": null }Present:
1122aab predates agent session linking, so there is no recorded session.Fromgit show: it addedvalidateScopeto enforce per-token scopes. I can
show the full diff if useful.
3. Bare path
User: "Give me context on src/middleware/limit.ts."
git log -n 1 -- src/middleware/limit.tsTake the SHA, run memory_commit_lookup, present commit plus linked session in the same shape as example 1.
Related skills
Caveman CommitGenerate terse, Conventional Commits messages that preserve intent without fluff or AI attribution.272k94k
Resolving Merge ConflictsQuickly understand, resolve, and commit merge conflicts without losing work or breaking their flow.183k193kGit Guardrails Claude CodePrevent Claude Code from accidentally running destructive git commands like force push, hard reset, or clean.175k193k
Using Git WorktreesGuarantee every new feature or implementation task runs inside a clean, isolated workspace without polluting the main branch or current working directory.149k263k
Git CommitGenerate accurate conventional commit messages and intelligently stage files directly from natural language requests.40.6k37.2k
Resolve Merge ConflictsQuickly understand and resolve Git merge conflicts without losing context or breaking changes.16.5k148How it compares
Choose commit-context over commit-history when investigating one blamed hunk rather than listing many agent-linked commits.
FAQ
What happens when a commit predates session linking?
The lookup returns commit: null. Report this as 'predates session linking' and show git show output without inventing session context.
How do I trace a specific function instead of line numbers?
Use git log -L :<function>:<file> to get the SHA that last modified that function, then query memory_commit_lookup.
Can I see what the agent was thinking during a commit?
Yes, if the session is linked. Use memory_recall on the session to retrieve importance >=7 observations from that agent run.
Is Commit Context safe to install?
skills.sh reports 1 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.