Skill Store 33

Commit Context

Trace a file, function, or line back to the agent session that produced its current commit.

by rohitg00 · Apache-2.0

The skill

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.

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

  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: null reported 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 TROUBLESHOOTING.md if memory_commit_lookup is not available.

Use this skill

Connect your agent to the Skill Store MCP server and ask for it by ref: rohitg00/commit-context-46346176263.

Download SKILL.md · Markdown version

Details

Publisher
rohitg00
Category
Software Development › Source control & code review
License
Apache-2.0
Updated
2026-10-18

References

More from rohitg00

  • Agentmemory Agents How agentmemory wires into host coding agents via the connect command.
  • Agentmemory Architecture How agentmemory is built, the iii engine primitives it runs on, its storage model, ports, and the…
  • Agentmemory Config Set up and diagnose local agentmemory, including MCP, environment variables, ports, and feature f…
  • Agentmemory Hooks The agentmemory plugin hooks that capture observations automatically across the agent session lif…

Related skills

  • Commit History List recent git commits linked to agent sessions, optionally filtered by branch or repo.
  • Code History Trace the git history of specific code — when a function, pattern, or file was added, modified, o…
  • Commit Archaeologist Reconstructs why code exists from local git history, including the introducing commit, later chan…
  • Trail Investigating git history, analyzing regression root causes, and performing code archaeology.
  • Gcc Git Context Controller (GCC) - Manages agent memory as a versioned file system under .GCC/.