菜单
Use when working on any Rust crate or workspace — before implementing features, after editing .rs files, when adding or removing dependencies, or when CI is failing. Symptoms - clippy warnings treated as errors, fmt diff in CI, wrong edition error, workspace member not found, slow test runs.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Deep codebase analysis — architecture health, test coverage gaps, tech debt, and actionable findings
Run pre-commit checks (fmt, clippy, test) then stage, commit, and push with a conventional message
Review staged or recent changes for correctness, style, and Rust conventions before committing
Use when SSHing into remote machines, looking up credentials, renaming Tailscale devices, or accessing services on the tailnet. Symptoms - SSH auth failures, too many authentication failures, command not found tailscale, need to find credentials for remote machines.
Use when mixing Tokio async code with synchronous blocking I/O libraries (tar, flate2, zip, csv), or when seeing "cannot block the current thread from within the async context" panics, or needing to stream async bytes into a sync reader.
Structured BAML schema edit → validate → test loop for the devloop project. Use when editing any *.baml file in crates/baml/baml_src/ — covers version parity gotchas, uvx invocation, regeneration workflow, and the analyze verify step.
| name | rust-conventions |
| description | Use when working on any Rust crate or workspace — before implementing features, after editing .rs files, when adding or removing dependencies, or when CI is failing. Symptoms - clippy warnings treated as errors, fmt diff in CI, wrong edition error, workspace member not found, slow test runs. |
Conventions for all Rust projects: dotfiles/toolz, Braid crates, Maestro, companion crates (personal-mcp, obfsck). Apply consistently — CI enforces these as hard failures.
Always edition = "2024" unless explicitly told otherwise. Verify before implementing:
grep 'edition' Cargo.toml
Run after every code change. CI enforces these as errors:
# Single crate
cargo fmt --check
cargo clippy -- -D warnings
cargo test
# Workspace
cargo fmt --all --check
cargo clippy --workspace -- -D warnings
cargo test --workspace
Use cargo-nextest for faster parallel test runs:
cargo nextest run # all tests
cargo nextest run -p <crate> # single crate
Verify nothing references it first — removing a used dep breaks the build silently until cargo check:
grep -r "use <crate_name>" src/
grep -r "<crate_name>::" src/
# Then remove from Cargo.toml and:
cargo check
workspace/
Cargo.toml # [workspace] members = ["crate-a", "crate-b"]
crate-a/
Cargo.toml # [package] + [dependencies]
src/
When adding a new crate, add it to [workspace] members in the root Cargo.toml.
# Check current members
cargo metadata --no-deps --format-version 1 | jq '.workspace_members'
cargo build -p <crate>
cargo test -p <crate>
cargo clippy -p <crate> -- -D warnings
cargo fmt -p <crate>
| Mistake | Fix |
|---|---|
| Wrong edition | Set edition = "2024" in [package] |
clippy passes locally but CI fails | Run with -- -D warnings to match CI |
| Removed dep still referenced | Grep usages before editing Cargo.toml |
cargo test slow | Use cargo nextest run |
| New crate not found in workspace | Add to [workspace] members in root Cargo.toml |
| fmt diff in CI | Run cargo fmt --all before committing |
fastembed/ONNX first build slow | Expected — transitive ONNX deps; not a hang |
rust-unsafe-env-mutation — set_var/remove_var unsafe + Mutex guard pattern for Rust 2024 testsasync-sync-bridge — spawn_blocking + SyncIoBridge + Handle::current() for async/sync I/O mixingtransparent-reader — pass-through Read wrapper for in-flight hashing/counting on streams