菜单
Use before every git push — mandatory quality gate, no exceptions
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
| name | pre-commit |
| description | Use before every git push — mandatory quality gate, no exceptions |
Before push. No exceptions.
change-review on the outgoing change — correctness, unhappy paths, tests. Any bug/issue → blocked. Fix it.clean-code-review on the same change — SRP/DRY/naming/coupling/dead-code/KISS. It tags violations as // TODO: clean-code - <score> - <CAT>: … markers.// TODO: clean-code - markers. Score > 0.5 → blocked. Fix it (or run refactor to clear the highest-scored one at a time).change-review is clean and no > 0.5 marker remains.Only then push.
基于 SOC 职业分类
Author and maintain PseudoScript (.pds) — C4-level architecture-as-code that compiles to diagrams and a doc site — as the single source of truth for spec-driven development. Use this skill whenever the user wants to model an application in PseudoScript, reverse-map / capture an existing app or codebase into a .pds model, drive development from a model (write the spec first, implement from it), capture business rules as code while keeping infrastructure (repositories, HTTP/controllers, persistence, queues, external APIs) as black boxes, write Gherkin-style `feature` behaviour specs, or reconstitute / generate a real implementation from a model. Trigger it on mentions of PseudoScript, `.pds`, "architecture as code", "C4 as code", "model the system", "spec-driven", "turn this app/codebase into pseudocode", or "what does the model say it should do" — even if the user doesn't name the language explicitly.
Multi-agent clean code audit — each principle gets its own agent
Find the unhappy paths an existing Cucumber/BDD suite doesn't cover and write them up as new Gherkin scenarios in the feature files. Use whenever the user wants to harden, stress, or find gaps in Cucumber tests, .feature files, or Gherkin scenarios, or mentions a "chaos monkey", negative testing, edge cases, failure modes, or unhappy paths. Trigger even on a casual "think of ways to break this" or "what are we not testing?" about a BDD codebase.
Review a set of changes (the staged diff, or a branch's diff) for correctness — before committing, pushing, or as a standalone pass
Write idiomatic, ownership-clean Rust. ALWAYS use this skill when writing or editing Rust — any .rs file, anything under crates/, Cargo.toml/Cargo manifests, or when the user asks to add a function, type, trait, test, or module in Rust. Grounds the model in established Rust idioms: error handling, ownership/borrowing, iterators, the type system, API design, and the clippy/rustfmt baseline. Trigger even when the user doesn't say "idiomatic" — any Rust authoring task qualifies.
Pick highest-scored clean-code TODO, fix it, stop. Loop handles repetition.
