菜单
Use when the task is call-relationship shaped: "who calls X", "what does X call", "trace this", references before a rename, shortest path, recursion, or hubs. Trigger before grepping a function name — grep misses dynamic dispatch. Do NOT use to locate a symbol (tracedecay:exploring-code).
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Prefer tracedecay tools for codebase exploration, graph queries, and memory recall.
Use when installing a TraceDecay checkout for live local development, refreshing the globally available binary without a release, or validating agents and the daemon against unmerged TraceDecay changes.
Use when installing a TraceDecay checkout for live local development, refreshing the globally available binary without a release, or validating agents and the daemon against unmerged TraceDecay changes.
Use when listing or reading agent-managed automation skills, viewing automation run artifacts, or inspecting skills owned by the standard Hermes user install without mutating them.
Use when you need LCM, session search, transcript search, raw past-session replay, scoped/time grep, summary-DAG drill-down, branch/worktree/commit history, workflow recovery, or compaction recovery; and when driving host LCM lifecycle preflight/compress/boundary/repair.
Use before writing a new function or helper (it may already exist), and before any rename, signature, or field change — the graph lists every call site.
| name | tracing-functions |
| description | Use when the task is call-relationship shaped: "who calls X", "what does X call", "trace this", references before a rename, shortest path, recursion, or hubs. Trigger before grepping a function name — grep misses dynamic dispatch. Do NOT use to locate a symbol (tracedecay:exploring-code). |
NO GREPPING FOR CALL SITES. The graph resolves dispatch; grep resolves text.
Announce: "Using tracedecay:tracing-functions to trace ."
| Question | Call |
|---|---|
| Resolve name → node ID first | tracedecay_find_exact_symbol / tracedecay_search (ladder: tracedecay:exploring-code) |
| Who calls X | tracedecay_callers (max_depth 1–2 first; widen only if unclear) |
| Many symbols at once | tracedecay_callers_for (node_ids[], one round-trip) |
| What X calls | tracedecay_callees (resolves trait dispatch; note dispatch_via_trait: true) |
| Path from A to B | tracedecay_call_chain (from_id, to_id, max_depth) |
| Every implementor / every body of a method | tracedecay_implementations |
| Every reference (rename prep) | tracedecay_rename_preview (preview only — nothing renames) |
| Cycles / hubs | tracedecay_recursion / tracedecay_hotspots / tracedecay_rank |
handle? Narrow depth/target set; tracedecay_retrieve
only when the omitted chain is needed.tracedecay:editing-safely.
"What breaks / which tests" → tracedecay:assessing-impact.select:tracedecay_callers,tracedecay_callees,tracedecay_call_chain,tracedecay_find_exact_symbol,tracedecay_rename_preview.tracedecay tool callers --node-id … etc. (see
tracedecay:using-the-cli). Never fall back to grepping call sites.Do not end without: the caller/callee tree or resolved path with dispatch
targets noted, and node IDs for any follow-up skill. Report any
tracedecay_metrics: line.