菜单
Create a new diagnostic parity test case. Use when the user asks to add a diagnostic test, create a new `tasks/diagnostic_tests/cases/<name>` case, or capture a false positive/false negative against npm `svelte/compiler` before implementation.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use whenever adding an e2e compiler-output test (our JS vs the reference compiler) — a new cluster case under `tasks/compiler_tests/`.
🧩 PARITY · Turn one divergence from the Original into a test per affected case (does not fix).
Use when starting any compiler task or session before touching parser/analyze/transform/ast/codegen/css/diagnostics code, before proposing a design or writing code, and when the task grows into a new layer and you need its PRD invariants.
🔪 SDT · verdict-directed review of backend codegen/transform. Use when auditing codegen/transform for smart-analyzer / dumb-codegen violations, or when porting a transform/codegen visitor from the Original.
The required unit-test format for `crates/**/src/**` — use when writing or reviewing a Rust `#[test]`, a test helper, or an `assert_*`. Not for `tasks/compiler_tests/` (use add-test) or `tasks/diagnostic_tests/` (use add-diagnostic-test).
PRD editorial standard for docs/. Use when writing a new PRD, extending one, or reviewing changes under docs/ — and when another skill needs the PRD rules.
| name | add-diagnostic-test |
| description | Create a new diagnostic parity test case. Use when the user asks to add a diagnostic test, create a new `tasks/diagnostic_tests/cases/<name>` case, or capture a false positive/false negative against npm `svelte/compiler` before implementation. |
Capture utility — not part of the PARITY chain. Creates a persistent diagnostic case for feature-first work. Do NOT use when you already have a
digfinding — that work lives undertasks/diagnostic_tests/cases/and is scoped by/dig. Use this skill only when registering a fresh, standalone diagnostic case before implementation.
snake_case. Stop if tasks/diagnostic_tests/cases/<name>/ exists.
Add tasks/diagnostic_tests/cases/<name>/case.svelte — the smallest component isolating one diagnostic behavior. Extend an existing case instead only when it already covers the same diagnostic code or syntax family and its case.svelte stays small.
Add config.json only when the diagnostic depends on compile options.
Run:
just generate
Creates case-svelte.json from npm svelte/compiler.
Never hand-edit case-svelte.json or case-rust.json.
Add #[rstest] case to tasks/diagnostic_tests/test_diagnostics.rs:
#[rstest]
fn <name>() {
assert_diagnostics("<name>");
}
just test-diagnostic-case <name>
Test writes case-rust.json for human comparison. Failure normal in test-first workflow. Report mismatch clearly. Do not "fix" reference snapshots.
Include:
/diagnose-diagnostics or /port specs/<feature>.md