Agent Skillsrohitg00/agentmemory › commit-context

commit-context

GitHub

追踪代码变更对应的 Agent 会话上下文。当用户询问代码来源、修改原因或特定位置背景时使用,通过 git 命令获取 SHA 并查询关联的 Agent 会话及观察记录,严禁臆测无记录的意图。

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

Trigger Scenarios

用户询问'这段代码为什么在这里' 用户想知道'这个文件/函数是谁写的'或'Agent 在此时做了什么' 需要查看代码库中特定位置的上下文信息

Install

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

Non-standard path

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

Use without installing

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

  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 ../_shared/TROUBLESHOOTING.md if memory_commit_lookup is not available.

Version History

  • a8e7d19 Current 2026-07-24 11:39

Same Skill Collection

plugin/skills/agentmemory-architecture/SKILL.md
plugin/skills/agentmemory-config/SKILL.md
plugin/skills/agentmemory-hooks/SKILL.md
plugin/skills/agentmemory-mcp-tools/SKILL.md
plugin/skills/agentmemory-rest-api/SKILL.md
plugin/skills/commit-history/SKILL.md
plugin/skills/forget/SKILL.md
plugin/skills/handoff/SKILL.md
plugin/skills/recall/SKILL.md
plugin/skills/recap/SKILL.md
plugin/skills/remember/SKILL.md
plugin/skills/session-history/SKILL.md
plugin/skills/write-agentmemory-skill/SKILL.md
plugin/skills/agentmemory-agents/SKILL.md

Metadata

Files
0
Version
d219763
Hash
11a6e724
Indexed
2026-07-24 11:39

Главная - Вики-сайт
Copyright © 2011-2026 iteam. Current version is 2.155.2. UTC+08:00, 2026-08-06 17:37
浙ICP备14020137号-1 $Гость$