Menu
Standard cargo workflow for build/test/lint cycles.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Dead-code forensics and spec cross-reference. Finds unreachable, orphaned, missing, or dormant code and classifies it DEAD, ZOMBIE, GHOST, or DORMANT. Use when the user says "find dead code", "what's unused", "what can I delete", "stale specs", "spec drift", "orphaned implementations", "find zombie code", or asks what's wired up vs sitting unused. Do NOT use for code-quality review (/age) or NIH/reinvented-wheel detection (/nih-audit).
Build lasting understanding of an unfamiliar codebase via a four-pillar model (Building Blocks, Entry Points, Infrastructure, Egress) plus an adaptive Socratic quiz, using tilth and Context7. Use when the user says "help me understand this codebase", "grok this repo", "onboard me", "learn this project", "memorize this codebase", "study this code", "walk me through this code", or "quiz me on this repo". Do NOT use for single-file scripts, repos under 500 LOC, or editing tasks — understanding only.
Map a concept end-to-end through a layered codebase — find the entry point, follow callers/callees layer by layer, and cross-check the impact radius. Use when the user says "trace this through", "map the X flow", "blast radius for Y", "what touches Z", "find the entry point for", "what's affected by (tilth), filesystem search (/scout), or dead-code detection (/ghostbuster).
Query coding-agent session logs (Claude, Codex, opencode) via DuckDB for usage analytics, tool patterns, error forensics, and routing decisions. Use when the user says "session analytics", "query my logs", "tool usage", "how often do I use", "check my sessions", "analyze my usage", or asks about tool/agent/skill behavior across sessions. Do NOT use for debugging current code, reading a single transcript, or questions about Claude's capabilities.
Render or apply a "routine env" — a named bundle of Claude Code plugins + MCP servers + skill packs defined in `envs/<name>.yaml` — into a setup-script body for Claude Cloud (Claude Code on the web), or apply it to the local machine. Use when the user says "set up a routine env", "provision my Claude Cloud environment", "install my cheese env", "render the setup script for <env>", "update my env", "scaffold a new env", or invokes "/routine-env". Do NOT use for cloud cron/scheduled agents that open PRs (that is `routine-scaffold`) or for a personal CLAUDE.md preferences overlay in a contributed repo (that is `claude-local`) — routine-env is about plugin/MCP/skill provisioning only.
Verify a spec's implementation against its requirements using Serena structural analysis, build verification, and test coverage. Use when the user says "verify the spec", "check spec implementation", "does this match the spec", "spec coverage", "verify acceptance criteria", or invokes /spec-verify; also after /cure to validate the result. Do NOT use for writing code or for general code review — use /age.
| name | cargo-workflow |
| description | Standard cargo workflow for build/test/lint cycles. |
Use this skill when working on Rust code that compiles via cargo.
cargo check # fast type-check (use first)
cargo test # run tests
cargo clippy # lint (treat warnings as errors)
cargo fmt # format
cargo nextest run if cargo-nextest is installed.cargo check --message-format=json when you need structured diagnostics.-p <crate> to avoid recompiling the world.--nocapture to see prints.cargo test -p <crate> <test_name> -- --exact --nocapture.--test-threads=1 to rule out concurrency.