commit-context

Agent Skills › rohitg00/agentmemory › commit-context

commit-context

GitHub

追踪代码文件、函数或行对应的 Agent 会话，解释代码变更原因及作者。通过 git blame/log 获取 SHA，查询关联的 Agent 会话详情与观察记录，提供代码上下文背景。

plugin/skills/commit-context/SKILL.md rohitg00/agentmemory

触发场景

询问代码为何存在询问修改时的 Agent 行为追溯代码作者

安装

npx skills add rohitg00/agentmemory --skill commit-context -g -y

更多选项

非标准路径

npx skills add https://github.com/rohitg00/agentmemory/tree/main/plugin/skills/commit-context -g -y

不安装直接使用

npx skills use rohitg00/agentmemory@commit-context

指定 Agent (Claude Code)

npx skills add rohitg00/agentmemory --skill commit-context -a claude-code -g -y

安装 repo 全部 skill

npx skills add rohitg00/agentmemory --all -g -y

预览 repo 内 skill

npx skills add rohitg00/agentmemory --list

SKILL.md

Frontmatter

{
    "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_recall when available.