memtrace-evolutionlisted

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).
syncable-dev/memtrace-public · ★ 474 · Code & Development · score 79

Install: claude install-skill syncable-dev/memtrace-public

## Overview Temporal analysis for "what changed in this repo between two points in time?" Works on both git commits and uncommitted working-tree saves. ## Required parameters — read before calling `get_evolution` **always** requires `repo_id` and `from`. There is no `days` parameter. | Parameter | Required | Type | Example | |---|---|---|---| | `repo_id` | yes | string | `"memdb"` | | `from` | yes | string | `"90d ago"`, `"2026-04-01T00:00:00Z"`, `"yesterday"` | | `to` | no | string | defaults to now; set to incident time when investigating | | `mode` | no | string | `"recent"` (default), `"compound"`, `"summary"`, `"overview"` | | `target` | no | string | symbol name or file path substring to scope results | | `branch` | no | string | branch filter | > **Parameter types:** MCP parameters are strictly typed. Numbers (`limit`, `cursor`, etc.) must be JSON numbers — not strings. Use `limit: 100`, never `limit: "100"`. ### Time-window parameters — do not confuse these tools | Tool | Time param | Example | Notes | |---|---|---|---| | `get_evolution` | **`from`** (required) | `"90d ago"` | optional `to`; **never** pass `days` | | `get_changes_since` | **`since`** (required) | `"2026-04-13T10:43:00Z"` | optional `until` | | `replay_history` | **`days`** (optional) | `90` | re-walks git history — different tool entirely | Common failure: `MCP error -32602: missing field 'from'` — you omitted `from` or passed `days` instead. ```json // CORRECT — 90-day overview { "repo_id":