Skip to content
Get packs

Commit Context Tracer

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

Source Download skill
Repository
rohitg00/agentmemory
Stars
30,083
Licence
Apache-2.0
Files
3 files

What it does

When you ask why a piece of code exists, this skill has the agent find the git commit that last changed that file, function, or line, then look up which recorded agent session produced that commit. It reports the commit details and the linked session summary, and avoids guessing intent when no session is recorded.

Great for

  • Developers reviewing unfamiliar code who want to know what the earlier work was for
  • Teams using the agentmemory memory system who want to connect commits to the agent sessions behind them

Skip it if

  • Repositories without the agentmemory memory system, since the memory_commit_lookup tool will be unavailable and only plain git output remains (the troubleshooting file covers this case)
  • Commits made before session linking existed, where the skill can only describe the diff, not the reasoning behind it

Try asking

  • “Why is this code here? src/auth/refresh.ts lines 40-52”
  • “Who wrote this function and what was the agent doing when it changed?”
  • “Show the agent session linked to the commit that last touched parseConfig”
Step-by-step guide: how to use Commit Context TracerInstall, first run, examples, tips and FAQs

Install in 3 steps

  1. 1

    Download the skill

    The ZIP contains the 3 original files, the Apache-2.0 licence and an attribution note.

    commit-context.zip
  2. 2

    Add it to your agent

    Claude Code (all projects)

    mkdir -p ~/.claude/skills && unzip commit-context.zip -d ~/.claude/skills/

    Claude Code / Agent SDK (this project only)

    mkdir -p .claude/skills && unzip commit-context.zip -d .claude/skills/

    Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.

  3. 3

    Ask for the task

    No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.

Get better results

  • Give a specific file, line range, or function name so the agent can run git blame or git log -L precisely
  • If the lookup returns no linked session, treat the commit as predating session linking and check the diff yourself with git show

What's inside

  • EXAMPLES.md
  • SKILL.md
  • TROUBLESHOOTING.md

Redistributed unmodified from rohitg00/agentmemory under the Apache-2.0 licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.