菜单
Triage and maintain TSZ diagnostic conformance. Use when investigating conformance regressions, accepted-regression drift, fingerprint-only failures, issue creation from conformance data, or focused parity fixes that must preserve the conformance gate.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/tsz-org/tsz --skill tsz-conformance命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Debug a Rust program or failing test with rdbg — set breakpoints (line, function, conditional, hit-count, panic, or watchpoint), run and step, read locals as real Rust values, change a variable mid-run, and jump to definition/hover/references via rust-analyzer. In tsz, reach for it on a runtime question reading hasn't localized — above all a wrong or extra (false-positive) diagnostic, where you break the diagnostic sinks and backtrace to the deciding frame instead of grepping emit sites. Skip it for missing-diagnostic bugs (nothing fires to break on) and small localized bugs a quick read already pins down.
Debug a Rust program or failing test with rdbg — set breakpoints (line, function, conditional, hit-count, panic, or watchpoint), run and step, read locals as real Rust values, change a variable mid-run, and jump to definition/hover/references via rust-analyzer. In tsz, reach for it on a runtime question reading hasn't localized — above all a wrong or extra (false-positive) diagnostic, where you break the diagnostic sinks and backtrace to the deciding frame instead of grepping emit sites. Skip it for missing-diagnostic bugs (nothing fires to break on) and small localized bugs a quick read already pins down.
Drive TSZ GitHub PRs through review, CI, and the merge queue. Use when checking PR status, debugging failing GitHub Actions, deciding whether a PR is WIP, marking draft PRs ready, enqueueing or verifying the queue, landing a PR, or interpreting TSZ CI gates.
基于 SOC 职业分类
正在显示 SKILL.md
| name | tsz-conformance |
| description | Triage and maintain TSZ diagnostic conformance. Use when investigating conformance regressions, accepted-regression drift, fingerprint-only failures, issue creation from conformance data, or focused parity fixes that must preserve the conformance gate. |
Conformance is a regression gate. Prefer checked-in artifacts and narrow filters; CI owns broad runs.
AGENTS.md and docs/plan/ROADMAP.md for conformance-affecting work.python3 scripts/conformance/query-conformance.py --dashboard
python3 scripts/conformance/query-conformance.py --campaigns
python3 scripts/conformance/query-conformance.py --fingerprint-only
python3 scripts/conformance/query-conformance.py --code TS2322
python3 scripts/conformance/query-conformance.py --code TS2322 --paths-only
Artifacts: conformance-detail.json, conformance-snapshot.json,
conformance-accepted-regressions.txt, conformance-shard-weights.json.
Semantics come from the pinned compiler, not from any other copy on the box. Run manual spot-checks through the wrapper so they match what the gate scores:
scripts/conformance/oracle.sh case.ts --strict --lib es2022 --target es2022
node scripts/node_modules/typescript/lib/tsc.js --version # Version 7.0.2
oracle.sh, not a bare tsc.js invocation. It runs the pinned
typescript@7.0.2 with the same --singleThreaded --stableTypeOrdering true
flags generate-tsc-cache.rs uses for TypeScript 7+. This is not just about
ordering: typescript@7.0.2 (typescript-go) reports a different diagnostic
set under --singleThreaded. A position-invalid import in a bare { } block
(or if/loop/try body) gets TS2307/TS2305 only single-threaded, not
under the default concurrent scheduler; the same import in a function, class
static { }, or namespace body gets neither, in both modes (#16413).
compare-to-parent.sh/conformance.sh score the single-threaded cache, so a
plain tsc.js case.ts silently disagrees with the gate — hand-oracling
without the flag reads a fix as passing that the gate then fails (this
mis-scoped #16409/#16411).TypeScript/ (submodule) and any container-global
/opt/**/node_modules/typescript are the 6.0 line. They are corpus and
test cases only — never the source of a semantic rule.ignoreDeprecations !== "6.0" from a 6.0.2
typescript.js, but 7.0 removed that grace window entirely (#16217).--target es5 was removed — it answers
error TS5108 and emits nothing else, and that line carries no file.ts(l,c):
prefix, so a row filter drops it and every row reads clean. strict also
defaults to true.Check raw output once before trusting a filtered sweep: an invalid invocation and a clean compile are indistinguishable after filtering.
./scripts/conformance/conformance.sh run --filter "<name>" --verbose
Keep filters precise. Let harnesses rebuild stale binaries when possible.
Classify: new/accepted/resolved/fingerprint-only/wrong-code/missing-code/ extra-code/crash/timeout/OOM. Then identify owner: relation, inference, narrowing, indexed/keyof/mapped/conditional/template, symbol resolution, diagnostic display, parser recovery, or emit-only.
Before coding, state the structural rule and adjacent cases. Behavior changes need owning-crate tests.
Accepted-regression drift: verify shard artifacts, update the accepted file only to match observed failing set, link/file issues for new accepts, and comment with numbers plus a provenance line.