菜单
Creates or updates a zo changelog file. Use when user says "changelog", "changelogs", "log changes", "update changelog", or after a commit that introduces notable changes. Do NOT use for trivial changes like typo fixes or formatting.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Validates code changes against zo's Three Prime Directives and architectural mandates. Use when reviewing PRs, planning new features, or when user says "check architecture", "validate design", "does this follow the rules", "architecture review", or "guard check". Do NOT use for simple formatting, typo fixes, or non-compiler code changes.
Runs the zo build pipeline (cargo build, clippy, tests) and analyzes failures with targeted fix suggestions. Use when user says "build", "check", "does it compile", "run clippy", "run tests", "ci check", or after making code changes. Do NOT use for non-Rust files or documentation-only changes.
Runs zo's test suite and intelligently analyzes failures. Reads failing test sources, traces the failure to compiler code, and suggests fixes. Use when user says "run tests", "what's failing", "test analysis", "fix failing tests", or "why is this test broken". Do NOT use for benchmarks or performance testing (use zo-perf-bench instead).
Reviews SIR-to-machine-code generation output for correctness and efficiency. Use when user says "review codegen", "check generated code", "codegen quality", "is the output correct", "review emitter output", or "arm output review". Do NOT use for source-level code review (use /blame instead) or performance benchmarking (use zo-perf-bench).
Benchmarks zo compiler phases against performance targets (10M LoC/s parse, 5M LoC/s analyze, 5M LoC/s codegen). Use when user says "benchmark", "perf", "how fast", "performance test", "speed check", "are we hitting targets", or "LoC/s". Do NOT use for general profiling of non-compiler code.
| name | zo-changelog |
| description | Creates or updates a zo changelog file. Use when user says "changelog", "changelogs", "log changes", "update changelog", or after a commit that introduces notable changes. Do NOT use for trivial changes like typo fixes or formatting. |
Create or update a changelog entry in crates/compiler/zo-notes/public/changelogs/.
ZO-CL<NN>-<DD>-<MM>-<YYYY>.md
<NN> — sequential number (zero-padded, 2 digits). check existing files and increment.<DD>-<MM>-<YYYY> — date in day-month-year format.ZO-CL01-01-04-2026.md, ZO-CL02-15-04-2026.md.ls crates/compiler/zo-notes/public/changelogs/
Determine the next sequence number and whether today's date already has a file.
# ZO-CL<NN> — <DD>-<MM>-<YYYY>.
## <crate name> (<crate>).
- bullet point describing the change. lowercase. concise but specific.
## tests.
- bullet point per test file added or updated.
codegen (zo-codegen-arm), parser (zo-parser), SiR (zo-sir)).tests section always last.