メニュー
This skill should be used when the user asks to "run gates", "validate rust", "pre-commit check", "run cargo validation", "check before committing", or wants to run the full Rust validation suite before a commit.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when the user runs "/insights-audit", asks to "validate the insights report", "audit the report against my projects", "check what the report got wrong", or wants to cross-check an /insights-generated HTML report against actual GitHub repos and local project directories.
This skill should be used when the user asks to "end session", "capture state", "session summary", "what changed this session", "summarize repos", "write session notes", or wants to capture multi-repo state at the end of a work session.
Fill in the Patterns & Surprises section of the latest session reflect file and write the completed review to .ctx/logs/self-review/. Use when the user runs "/self-review", asks to "fill in the reflect", "write the session review", or "what patterns did we hit".
Use when working on the rslm project — Recursive Language Model inference engine in Rust. Triggers on "rslm", "RLM", "recursive language model", "rhai built-ins", "ctx_grep", "ctx_slice", "rlm_call", "rslm-core", "rslm-providers", "rslm-store", or any question about running queries, ingesting documents, or writing Rhai scripts for the RLM loop.
This skill should be used when the user asks to "review this diff", "ai review", "security review my changes", "review before push", "check my code for issues", or wants an LLM-based security and correctness review of uncommitted or unpushed changes.
This skill should be used when the user asks to "generate commit message", "write a commit msg", "ai commit", "generate a conventional commit", "write my commit", or wants an LLM to draft a commit message from the staged diff.
| name | cargo-gate |
| description | This skill should be used when the user asks to "run gates", "validate rust", "pre-commit check", "run cargo validation", "check before committing", or wants to run the full Rust validation suite before a commit. |
| model | sonnet |
| effort | high |
| allowed-tools | ["Bash","Read","Glob"] |
Run the full Rust validation suite before committing. The cargo xtask pre-commit gate
always takes priority — this skill wraps it and adds structured pass/fail reporting.
Always run stages in this order:
cargo xtask pre-commit — runs fmt-check + clippy + release build (canonical gate, always first)cargo xtask pre-commit
If cargo xtask pre-commit is not available (no xtask in workspace), fall back to:
cargo fmt --check && cargo clippy -- -D warnings && cargo test && cargo check --workspace
Never skip cargo xtask pre-commit when it exists. It is the canonical gate.
After running, present a structured summary:
STAGE RESULT
fmt PASS
clippy PASS (or: FAIL — 3 warnings promoted to errors)
test PASS (or: FAIL — 2 tests failed)
check PASS
If any stage fails, show the first 20 lines of error output for that stage.
When clippy produces suggestion-level warnings (not errors), offer:
"clippy has N suggestions. Apply auto-fixes? (yes/no/show-diff)"
If yes: run cargo clippy --fix --allow-staged. Always show the diff before applying.
Never auto-apply without confirmation.
cargo xtask pre-commit on minibox runs: fmt-check → clippy → release build.
It does NOT run cargo test by default. Add test stage separately if needed.
Invoke before every commit on Rust projects. Pairs with git-guard — run cargo-gate
first, then git-guard to confirm merge strategy before committing.
references/xtask-patterns.md — xtask detection, workspace vs crate gates, fallback
stage sequence, clippy fix workflow, common failure patterns, minibox xtask profile