commit-context
This skill traces a code file, function, or specific line back to the AI Agent session that produced its current commit. When users need to understand 'why this code is here,' 'what the Agent was doing during the change,' or require context for a specific location in the codebase, this Skill provides crucial historical background and decision-making basis, significantly improving code comprehension and troubleshooting efficiency.
npx skills add https://github.com/rohitg00/agentmemory --skill commit-contextBefore / After Comparison
1 组Before this skill, users or developers had to manually execute commands like `git blame` or `git log`, then attempt to infer the intent of code changes from commit messages, or spend significant time searching for documentation and communicating. This process was inefficient and often missed critical AI Agent decision-making information.
This skill can quickly trace code changes back to the AI Agent session that produced the commit, directly providing the context, purpose, and relevant observation records of the change. This significantly reduces manual analysis and communication time, ensuring developers accurately understand the Agent's operational logic.
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.
User Reviews (0)
Write a Review
No reviews yet
Statistics
User Rating
Rate this Skill