/memtrace-continuous-memory
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.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/memtrace-continuous-memory
Context 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
SKILL.md
memtrace-continuous-memory.SKILL.mdname: 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."
Overview
Keep the knowledge graph live while editing. `watch_directory` triggers incremental re-indexing on file saves (~80 ms typical latency after debounce).
Required parameters — `watch_directory`
| 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).
Steps
1. Confirm indexed
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).
2. Start watching
See JSON above. Returns immediately; watcher runs in background.
3. Confirm active watches
list_watched_paths()
Response shape: see [Output](#output).
4. Edit normally
Next `find_symbol` / `get_symbol_context` call sees saved changes after debounce (~500 ms) + incremental persist (~80 ms).
5. Stop watching (kill switch)
`unwatch_directory`:
{ "path": "/abs/path/to/repo" }Idempotent — unwatching an already-unwatched path is a no-op.
Latency expectations
| Stage | Typical | |---|---| | Debounce | **500 ms** (MCP schema) | | Incremental persist | ~80 ms | | Save → queryable | ~80–150 ms after debounce |
Output
`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.
Common Mistakes
| 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** |
Read more
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."
Overview
Keep the knowledge graph live while editing. `watch_directory` triggers incremental re-indexing on file saves (~80 ms typical latency after debounce).
Required parameters — `watch_directory`
| 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).
Steps
1. Confirm indexed
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).
2. Start watching
See JSON above. Returns immediately; watcher runs in background.
3. Confirm active watches
list_watched_paths()
Response shape: see [Output](#output).
4. Edit normally
Next `find_symbol` / `get_symbol_context` call sees saved changes after debounce (~500 ms) + incremental persist (~80 ms).
5. Stop watching (kill switch)
`unwatch_directory`:
{ "path": "/abs/path/to/repo" }Idempotent — unwatching an already-unwatched path is a no-op.
Latency expectations
| Stage | Typical | |---|---| | Debounce | **500 ms** (MCP schema) | | Incremental persist | ~80 ms | | Save → queryable | ~80–150 ms after debounce |
Output
`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.
Common Mistakes
| 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 · Hermes · VS Code · Windsurf.
Repo: syncable-dev/memtrace-public
Other skills on memtrace-public.
- /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, fetch/client calls, REST surface, service dependencies, cross-repo dependencies, or API topology. Do not use Grep, Glob, rg,
Open skill - /memtrace-change-impact-analysis
Compute what a planned source-code change will break — blast radius, affected processes, cross-repo callers, temporal stability, and Cortex decision-memory constraints — and produce a risk-rated change plan. Use for multi-symbol or multi-part edits, refactors, API changes,
Open skill - /memtrace-cochange
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 coupling, co-change, what changes with this, hidden dependencies, or what else needs to move for source code. Do not use git
Open skill - /memtrace-code-review
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, post Memtrace review comments, create a PR with a review step, or publish local graph-backed review findings to GitHub.
Open skill - /memtrace-codebase-exploration
Map an indexed source-code repo into a structured overview — scale, communities, central symbols, execution flows, API surface, recent activity. Use when the user wants to explore, understand, onboard to, map, or get an overview of an indexed source-code repo, architecture,
Open skill - /memtrace-daily
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 briefing (what changed in the last 24h with complexity deltas), hotspots (complexity × churn refactor priorities), or a
Open skill

