← ClaudeAtlas

tosslisted

File a reproducible bug report directly into another registered x-kit project's inbox — captures a repro command + output (secret-redacted), a fix direction, writes a durable local outbox record, and best-effort notifies the target via mem-mesh. Use when a repro found while working in project A actually implicates project B's code, or the user says "toss this to <project>" / "이거 다른 프로젝트 버그같은데 던져줘".
x-mesh/xm · ★ 0 · AI & Automation · score 70
Install: claude install-skill x-mesh/xm
# x-toss — Cross-Project Bug Handoff ## Overview When work in project A surfaces a bug that actually belongs to project B, `/xm:toss` files the report directly into B without switching sessions or directories. It: 1. Captures the repro command + its actual output (redacted for secrets, tail-bounded) 2. Writes a durable record into the SENDER's own `.xm/outbox/<id>.json` via the CLI — this succeeds even if step 3 never happens 3. **You (the skill), not the CLI, deliver a pin + memory into the TARGET project's mem-mesh space** by calling the `mcp__mem-mesh__pin_add` / `mcp__mem-mesh__add` tools directly, using the exact arguments the CLI printed in step 2 4. You record the returned `pin_id`/`memory_id` back into the same outbox item via `xm inbox record` Toss never touches the target project's `.xm/` directly (ownership invariant) — only its own outbox. **The CLI itself makes zero network calls** — it has no MCP session and no auth, so it cannot call mem-mesh. Delivery only happens when you, running inside Claude Code with a live MCP session, make the calls yourself. ## When to Use - "이거 우리 프로젝트 버그가 아니라 git-kit 버그 같은데 던져줘" / "toss this to git-kit" - A repro command's output implicates another **registered** project's code, not this one - You want the other project to see the report next session without opening this repo ## Do NOT Use When - The bug is in THIS project — just fix it, or file it with `/xm:later` instead. - The target isn't a registered x-kit pr