memtrace-episode-replay

Solid

Replay the graph diff of one episode — a single git commit or working-tree save — to inspect what it changed: added/modified/removed symbols and edges. Use when the user asks what one commit or save changed in the graph, why code looks this way, or wants to inspect implementation attempts, reversions, past reasoning, or abandoned approaches across commits and working-tree episodes. Do not use git log or Grep for graph-level episode diffs; Memtrace replays indexed episode records. Do NOT use for module-level summaries or date-range change history — use memtrace-evolution.

Code & Development 469 stars 41 forks Updated 5 days ago NOASSERTION

Install

View on GitHub

Quality Score: 81/100

Stars 20%
89
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

## Overview Replay the graph diff for **one episode** (a single git commit or working-tree save). Shows which nodes/edges were added, modified, or removed in that episode — not a multi-episode time-range narrative. Use `get_evolution(mode: "recent")` to **find** episode IDs and timestamps, then drill into a specific episode with this tool. ## Episode selector — pick one | Approach | Parameters | |---|---| | Known episode UUID | `episode_id` | | Newest episode in repo | `repo_id` + `episode_index: 0` | | Nth newest | `repo_id` + `episode_index: N` | **There is no `from` / `to` / `include_working_tree` on this tool.** ## Optional filters (large commits) | Param | Purpose | |---|---| | `symbol` | Scope to one symbol name | | `file_path` | Substring filter on record paths | | `kind` | e.g. `"Function"`, `"CALLS"` | | `mode` | `"graph_summary"` for digest on huge commits | | `compress` | default `true` — collapse identical-hash modifications | | `limit` / `cursor` | Pagination per bucket (default limit 200) | Full parameter spec for every Memtrace tool: `references/mcp-parameters.md` (bundled at the memtrace-skills plugin root). ## Steps ### 1. Find the episode to inspect From `get_evolution`: ```json { "repo_id": "memdb", "from": "7d ago", "mode": "recent", "limit": 20 } ``` Each entry has `episode` metadata including `id` (use as `episode_id`) and `reference_time`. Or use `episode_index: 0` for the newest episode without knowing the UUID. ### 2. Call `get_episode_...

Details

Author
syncable-dev
Repository
syncable-dev/memtrace-public
Created
5 months ago
Last Updated
5 days ago
Language
Python
License
NOASSERTION

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Solid

memtrace-evolution

Trace source-code change history from Memtrace's symbol-level temporal memory. Use when the user asks about change history, recent modifications, what changed since a date, symbol timeline, evolution, unexpected changes, or incident timelines. Do not use git log, git diff, Grep, or manual file search to reconstruct history. Do NOT use for current-state architecture overviews (use memtrace-codebase-exploration) or for replaying one commit/save's graph diff (use memtrace-episode-replay).

469 Updated 5 days ago
syncable-dev
AI & Automation Solid

memtrace-session-continuity

Catch up on everything that changed in an indexed source-code repo since the last session, using stored session anchors and Memtrace change memory. Use when the user asks to continue, catch up, resume, see what changed while away, recover prior context, or orient at session start without guessing timestamps. Do not use git log, Grep, or manual file search for catch-up; Memtrace provides session anchors and change memory.

469 Updated 5 days ago
syncable-dev
Code & Development Solid

memtrace-incident-investigation

Investigate source-code bugs, incidents, regressions, production issues, and failures to root cause with Memtrace symbol search, impact, call graph, and temporal history. Use when the user asks about root cause analysis, what broke, or what changed when debugging a failure. Do not start with Grep, Glob, rg, find, or manual file search for code causes. For plain what-changed questions without a failure, use memtrace-evolution.

469 Updated 5 days ago
syncable-dev