commit-context
rohitg00/agentmemory
Trace code back to the agent session that created it—answer 'why is this here' and 'what was the agent doing'.
What is commit-context?
Traces a file, function, or line to its commit SHA, then looks up the linked agent session that produced it. Use when you need to understand the intent or context behind a specific code change.
- Find commit SHA using git blame, git log, or git show
- Look up the linked agent session for that commit
- Display commit details (SHA, branch, author, message) and session metadata
- Retrieve high-importance observations from the session when available
- Report commits that predate session linking without fabricating context
How to install commit-context
npx skills add https://github.com/rohitg00/agentmemory --skill commit-context- Git repository with commit history
- agentmemory installed and memory_commit_lookup available
- Commits linked to agent sessions (older commits may return null)
How to use commit-context
- 1.Identify the file, function, or line range you want context for
- 2.Use git blame, git log, or git show to find the commit SHA
- 3.Call memory_commit_lookup with the full SHA
- 4.Review the returned commit and linked session details
- 5.Use memory_recall to dig deeper into high-importance observations if needed
Use cases
- User asks 'why is this code here'—trace the line to its commit and session
- User asks 'what was the agent doing when this changed'—retrieve session observations
- Understand the intent behind a specific function or file change
- Investigate who made a change and in what context
- Audit code provenance when commits are linked to agent sessions
- Developers reviewing code history
- Agents investigating their own or prior session outputs
- Teams auditing changes made by coding agents
- Code reviewers needing context on specific changes
commit-context FAQ
The lookup returns commit: null. Report this as 'predates session linking' and show the git diff instead—do not invent session intent.
Use git blame -L <start>,<end> <file> for a line range, git log -L :<function>:<file> for a function, or git log -n 1 -- <file> for a whole file.
Use the commit-history skill to list many agent-linked commits together.
Check ../_shared/TROUBLESHOOTING.md for setup and configuration steps.
No—report only what git and the lookup return. Quote session details verbatim and do not fabricate agent reasoning.
Full instructions (SKILL.md)
Source of truth, from rohitg00/agentmemory.
name: commit-context description: Trace a file, function, or line back to the agent session that produced its current commit. Use when the user asks "why is this code here", "what was the agent doing when this changed", "who wrote this", or wants context on a specific location in the codebase. argument-hint: "[file, function, or line]" user-invocable: true
The user wants commit context for: $ARGUMENTS
Quick start
git blame -L 40,52 src/auth/refresh.ts # -> SHA 9a1b2c3d
memory_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
- 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. - Look it up:
memory_commit_lookup { "sha": "<full-sha>" }. - 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_recallwhen 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.
Related skills
More from rohitg00/agentmemory and the wider catalog.
commit-history
List recent git commits linked to agent sessions, filtered by branch or repo.
forget
Delete specific memories from agentmemory with explicit user confirmation.
handoff
Resume the most recent agent session for your project, picking up from any unanswered question.
lesson
Save confidence-weighted behavioral rules that resurface before similar work.
memory-discipline
Recall before work, save at decisions—the discipline that makes agent memory actually pay off.
recall
Search past observations and learnings using hybrid BM25+vector+graph search.