菜单
Use when compiler or type errors are in play: pasted "cargo check"/clippy/tsc/pyright output, a failed build, or a planned type check. Trigger before running those in the shell — tracedecay maps diagnostics to the enclosing symbol with callers. Do NOT use for test failures.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/ScriptedAlchemy/tracedecay --skill fixing-build-and-type-errors命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Use when Review self-improvement automation runs and activation policy.
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.
TraceDecay Dev: Use when auditing, testing, debugging, or improving TraceDecay hook hint behavior, especially Codex/Claude/Cursor hint injection, verbosity, repetition, dedupe, token efficiency, real transcript examples, synthetic scenarios, or `src/hooks/tool_hints*` changes.
基于 SOC 职业分类
正在显示 SKILL.md
| name | fixing-build-and-type-errors |
| description | Use when compiler or type errors are in play: pasted "cargo check"/clippy/tsc/pyright output, a failed build, or a planned type check. Trigger before running those in the shell — tracedecay maps diagnostics to the enclosing symbol with callers. Do NOT use for test failures. |
NO RAW `cargo check`/`tsc` IN THE SHELL WHEN A STRUCTURED PATH EXISTS,
AND NO FIX WITHOUT THE ENCLOSING SYMBOL AND ITS CALLERS IN VIEW.
Announce: "Using tracedecay:fixing-build-and-type-errors."
| Situation | Call | Cost |
|---|---|---|
| Compiler output already on hand (pasted or captured) | tracedecay_diagnose (cargo_output, include_callers?) — parses text, maps each error to the smallest containing node with up to 5 callers. Rust/cargo only. | Free — no toolchain run |
| Need fresh diagnostics | tracedecay_diagnostics (scope: workspace | package+name | file+path) — multi-language (cargo/tsc/pyright), structured, node-mapped. | Heavy — first run on a fresh tree can take minutes (target dir /tmp/tracedecay-target/<project_id>/diagnostics); later runs sub-second |
Always prefer the free row. Respect the host's approval/run-mode before running fresh toolchain checks.
tracedecay:exploring-code ladder;
widen with tracedecay_impact when the fix touches a hub.tracedecay:editing-safely.diagnose, or diagnostics with scope: "file"), then verify behavior via
tracedecay:assessing-impact.select:tracedecay_diagnose,tracedecay_diagnostics,tracedecay_search,tracedecay_signature,tracedecay_callers.tracedecay tool diagnose --cargo-output @/tmp/err.txt (the @
reads a file) / tracedecay tool diagnostics --scope file --path … (see
tracedecay:using-the-cli). Only if the CLI is also unavailable, run the
raw toolchain and paste its output back through diagnose when possible.Do not end while errors remain unexplained: deliver the grouped diagnostics
with enclosing symbols and callers, the applied fix per error class, and a
clean re-check (or a precise statement of what still fails and why). Report
any tracedecay_metrics: line.