菜单
Use for TypeScript/ECMAScript compatibility changes. Defines decision order for semantic compatibility, WASI lowering, Node fallback.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | compatibility |
| description | Use for TypeScript/ECMAScript compatibility changes. Defines decision order for semantic compatibility, WASI lowering, Node fallback. |
The input language is TypeScript plus ECMAScript runtime semantics. Do not require AssemblyScript-only syntax, primitive types, intrinsics, or standard library behavior from users.
A compatibility change is not “done” until the relevant test gates are green; run the commands below and record outcomes. Without mise, use mise with the same name. First time: mise trust (docs).
mise run fmt
mise run clippy
mise run nextest
mise run test262 (and pipe through mise run test-differential-reporter with the project’s file conventions; see scripts headers)mise run reference-coverage (as documented for that script)process.argv maps to WASI args when possible.process.env maps to WASI environ and a runtime facade when possible.host.<domain>.<function> in the capability manifest.Every compatibility change needs a classified test status: pass, fail, unsupported, blocked, or skip-with-reason.
// Fixtures/builtins-and-io/stdin.ts
process.stdin.read();
mise run nextest
# Test status: pass (Node.js parity confirmed)
# Update docs/05-compatibility-and-semantics.md with supported feature
mise run fmt
mise run clippy
mise run nextest
mise run test262 -- --sample 50 --jobs 4
Use when adding/editing scripts under scripts/. Covers layout conventions, shell rules, output contracts, validation.
Use for ast-grep lint rules when general-purpose linters cannot express patterns. Covers config, rules, testing, CI integration.
Use when adding/editing docs under docs/. Enforces state separation between final-state docs, current-state, issues, and historical state.
Use when adding/editing/moving/renaming fixtures under fixtures/. Covers naming rules, content rules, inventory, reference updates.
Use when acting as gatekeeper/reviewer for PRs or agent outputs. Covers sources of truth, required commands, reject conditions, domain checklists.
Use when resolving git merge conflicts, especially after git pull --rebase or git merge origin/master