القائمة
Run Rust tests. Use when testing, or as a validation gate before claiming a Rust task is complete. Run `cargo build` and `cargo test` before declaring any Rust code change done.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Web search and content extraction via Brave Search API. Use for searching documentation, facts, or any web content. Lightweight, no browser required.
Interactive browser automation via Chrome DevTools Protocol. Use when you need to interact with web pages, test frontends, or when user interaction with a visible browser is required.
Create software architecture diagrams using the C4 model (Context, Containers, Components, Code). Applies Simon Brown's diagramming principles: titles, legends, directional arrows, explicit text, abstractions-first. Use when user asks for architecture diagrams, system diagrams, C4 diagrams, or wants to document software structure.
Ultra-compressed communication mode. Cuts token usage ~75% by dropping filler, articles, and pleasantries while keeping full technical accuracy. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman.
Query the cerebro cortex knowledge base for project context, journal entries, intent/goals, TODOs, and statistics. Use when the user asks about their projects, wants to read journal entries, check goals/intentions, search for TODOs across repos, or get an overview of their activity data. Also use when browsing what the user has been working on across their side projects.
Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.
| name | cargo-test |
| description | Run Rust tests. Use when testing, or as a validation gate before claiming a Rust task is complete. Run `cargo build` and `cargo test` before declaring any Rust code change done. |
cargo test
cargo test <pattern>
cargo test --workspace
cargo test -p <package>
cargo test -- --show-output
Before declaring a Rust task complete, verify:
cargo build — compiles and linkscargo test --workspace — tests passIf either fails, fix the root cause and re-run. Do not claim the task is done until both succeed.
--doc.--no-fail-fast runs all tests even after the first failure, useful for seeing the full picture.--lib, --bins, --tests filter by target type.--release) may compile optimizations that mask timing bugs.cargo build before cargo test if you see linking errors.