/memtrace-fleet-record-episode
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.
- 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-fleet-record-episode
Context 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
SKILL.md
memtrace-fleet-record-episode.SKILL.mdname: 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."
Overview
`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.
Call it
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).
The result: conflict_class
- **A → proceed.** Additive, order-independent.
- **B → re-read, then proceed.** Non-destructive overlap; re-read the shared
symbols so you build on current state.
- **C → a decision is needed.** A destructive change overlaps another agent's
work. The response includes:
- `escalation_id` — the decision's id.
- `mediation_request` — the judging task (every agent's `assignment` + the
contested symbols). If you're asked to judge, call `fleet_submit_verdict`.
- `next_action` — poll `fleet_get_escalation({escalation_id, agent_id})` until
`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.
After recording
- Class A/B → continue.
- Class C → enter the decision loop (see `memtrace-fleet-first`). Don't keep
editing the contested symbols until your directive is `proceed`.
- Every recorded episode is logged and persists as the fleet's reviewable audit
trail. Review history with `fleet_query_episodes({repo_id, node?, conflict_class?})`.
Output
{
"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"
}Read more
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."
Overview
`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.
Call it
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).
The result: conflict_class
- **A → proceed.** Additive, order-independent.
- **B → re-read, then proceed.** Non-destructive overlap; re-read the shared
symbols so you build on current state.
- **C → a decision is needed.** A destructive change overlaps another agent's
work. The response includes:
- `escalation_id` — the decision's id.
- `mediation_request` — the judging task (every agent's `assignment` + the
contested symbols). If you're asked to judge, call `fleet_submit_verdict`.
- `next_action` — poll `fleet_get_escalation({escalation_id, agent_id})` until
`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.
After recording
- Class A/B → continue.
- Class C → enter the decision loop (see `memtrace-fleet-first`). Don't keep
editing the contested symbols until your directive is `proceed`.
- Every recorded episode is logged and persists as the fleet's reviewable audit
trail. Review history with `fleet_query_episodes({repo_id, node?, conflict_class?})`.
Output
{
"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 · 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-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
Open skill

