Menu
Trace a file, function, or line back to the agent session that produced its current commit
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Diagnose mempalace setup (config, palace path, MCP, FTS/index health)
List or inspect people/project entities tracked in the mempalace graph
Mine a project directory into the mempalace corpus (drawers, rooms, wings)
Hybrid search over the mempalace corpus (BM25 + vectors + optional graph)
Show mempalace palace status (drawers, wings, rooms, health)
List recent git commits linked to agent sessions, optionally filtered by branch or repo
| name | commit-context |
| description | Trace a file, function, or line back to the agent session that produced its current commit |
| argument-hint | [file, function, or line] |
| user-invocable | true |
The user wants commit context for: $ARGUMENTS
Run git blame/git log, get the SHA, call memory_commit_lookup.
Understand why a line of code exists by linking it to the agent session that created it.
git blame -L <start>,<end> <file>git log -L :<function>:<file>git log -n 1 -- <file>memory_commit_lookup with sha: "<full-sha>".WRONG -- inventing a session for unlinked commits:
// "memory_commit_lookup returned null so I made up a session"
RIGHT -- stating the fact:
// No linked session found. This commit predates session linking.
WRONG -- using short SHA:
// memory_commit_lookup expects a full SHA, not the 7-char abbreviation
If MCP is unavailable: GET $MEMPALACE_URL/commits/{sha} with Authorization: Bearer $MEMPALACE_SECRET.
See
_shared/TROUBLESHOOTING.mdandEXAMPLES.mdfor more.