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,…
Record an edit you just made in a fleet and get its conflict class (A/B/C) against agents on your branch. Use when you have just finished an edit, when the user says 'I just changed X', or when completing a refactor step while other agents share your repo+branch. Returns
$ npx -y skills add syncable-dev/memtrace-public --skill memtrace-fleet-record-episode --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/memtrace-fleet-record-episodeContext preview
The summary Claude sees to decide when to auto-load this skill.
Record an edit you just made in a fleet and get its conflict class (A/B/C) against agents on your branch. Use when you have just finished an edit, when the user says 'I just changed X', or when completing a refactor step while other agents share your repo+branch. Returns
name: memtrace-fleet-record-episode description: "Record an edit you just made in a fleet and get its conflict class (A/B/C) against agents on your branch. Use when you have just finished an edit, when the user says 'I just changed X', or when completing a refactor step while other agents share your repo+branch. Returns conflict_class + replan_hint; a Class C returns an escalation_id and mediation_request that starts the decision loop. Do not finish a coordinated edit without recording it."
`fleet_record_episode` is step 3 of the fleet protocol: record the edit you just made and learn whether it collided with another agent on your branch.
fleet_record_episode({
repo_id: "myrepo",
branch: "session/auth-revamp",
agent_id:"agent-a",
touched: ["auth::verify_token"],
intent: {"refactor": {"pattern": "change_signature"}}
})Full parameter spec for every Memtrace tool: `references/mcp-parameters.md` (bundled at the memtrace-skills plugin root).
symbols so you build on current state.
work. The response includes:
contested symbols). If you're asked to judge, call `fleet_submit_verdict`.
`your_directive` ≠ `wait`, then `proceed` / `defer` / `review`.
Class is computed **only against agents on your branch**. Agents on other branches never make your edit a Class C.
editing the contested symbols until your directive is `proceed`.
trail. Review history with `fleet_query_episodes({repo_id, node?, conflict_class?})`.
{
"conflict_class": "C", // "A" | "B" | "C"
"replan_hint": "re-read auth::verify_token before continuing",
// Class C only — absent for A/B:
"escalation_id": "esc-01J9...",
"mediation_request": { /* each agent's assignment + contested symbols */ },
"next_action": "poll fleet_get_escalation until your_directive != wait"
}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…
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,…