memtrace-api-topology
Map API endpoints, outbound HTTP calls, and cross-repo service topology in indexed source code. Use when the user asks about API endpoints, HTTP routes,…
Keep the Memtrace index fresh while editing by watching a repo for live, incremental re-indexing. Use when the user asks to keep Memtrace fresh while editing, watch a repo, enable live or incremental indexing, set up always-on memory (meaning Memtrace index watching, not generic
$ npx -y skills add syncable-dev/memtrace-public --skill memtrace-continuous-memory --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/memtrace-continuous-memoryContext preview
The summary Claude sees to decide when to auto-load this skill.
Keep the Memtrace index fresh while editing by watching a repo for live, incremental re-indexing. Use when the user asks to keep Memtrace fresh while editing, watch a repo, enable live or incremental indexing, set up always-on memory (meaning Memtrace index watching, not generic
name: memtrace-continuous-memory description: "Keep the Memtrace index fresh while editing by watching a repo for live, incremental re-indexing. Use when the user asks to keep Memtrace fresh while editing, watch a repo, enable live or incremental indexing, set up always-on memory (meaning Memtrace index watching, not generic agent memory), or make just-saved source code queryable immediately. Do not fall back to repeated Grep or manual rescans; configure Memtrace watching."
Keep the knowledge graph live while editing. `watch_directory` triggers incremental re-indexing on file saves (~80 ms typical latency after debounce).
| Param | Required | Notes | |---|---|---| | `path` | yes | Absolute directory path | | `repo_id` | yes | Must already be indexed | | `branch` | no | default `"main"` |
{ "path": "/abs/path/to/repo", "repo_id": "memdb" }Full parameter spec for every Memtrace tool: `references/mcp-parameters.md` (bundled at the memtrace-skills plugin root).
list_indexed_repositories()
Run `index_directory` first if missing (poll `check_job_status`; stop after ~5 minutes and report the job id — see memtrace-index).
See JSON above. Returns immediately; watcher runs in background.
list_watched_paths()
Response shape: see [Output](#output).
Next `find_symbol` / `get_symbol_context` call sees saved changes after debounce (~500 ms) + incremental persist (~80 ms).
`unwatch_directory`:
{ "path": "/abs/path/to/repo" }Idempotent — unwatching an already-unwatched path is a no-op.
| Stage | Typical | |---|---| | Debounce | **500 ms** (MCP schema) | | Incremental persist | ~80 ms | | Save → queryable | ~80–150 ms after debounce |
`watch_directory` returns an immediate acknowledgment; the watcher runs in the background. `list_watched_paths` returns:
{
"watches": [
{ "path": "...", "repo_id": "...", "branch": "...", "started_at": "...", "origin": "..." }
],
"count": 1
}There is **no `persist_ms`** field in this response.
| Mistake | Reality | |---------|---------| | `watch_directory(path=...)` without `repo_id` | **Both required** | | Watching unindexed repo | Index first | | Expecting `persist_ms` from `list_watched_paths` | Field not in MCP response | | Debounce "50 ms" | Schema documents **500 ms** |
Structural memory for AI coding agents. Bi-temporal graph, MCP-native, zero LLM calls. Cursor · Claude Code · Codex · DeepSeek Harness · Hermes · VS Code · Windsurf.
Repo: syncable-dev/memtrace-public
Map API endpoints, outbound HTTP calls, and cross-repo service topology in indexed source code. Use when the user asks about API endpoints, HTTP routes,…
Compute what a planned source-code change will break — blast radius, affected processes, cross-repo callers, temporal stability, and Cortex decision-memory…
Find files that historically co-change with a target symbol or file, ranked by co-occurrence across git episodes. Use when the user asks about historical…
Review GitHub pull requests with Memtrace's local graph-backed review engine. Use when the user asks to review a GitHub pull request, run Memtrace code review,…
Map an indexed source-code repo into a structured overview — scale, communities, central symbols, execution flows, API surface, recent activity. Use when the…
Orient at the start of a coding session, review what recently changed in a repository, and self-audit after completing work. Use when the user wants the daily…