rust-development_skill

Overview

This skill runs a complete Rust development workflow for the Miyabi project, automating build, test, lint, and format checks. It enforces type safety, test coverage, and code quality before commits or releases. Use it to standardize CI/local checks and reduce regressions during development.

How this skill works

The skill executes prioritized cargo commands in optimized patterns: quick checks, full pre-commit cycles, clean builds, and release flows. It inspects compilation status, test results, Clippy warnings, and formatting diffs, returning a concise summary of Build, Tests, Clippy, Format, and Docs outcomes. Parallelism and incremental build options are applied when appropriate to speed up iteration.

When to use it

• During active development for fast feedback (quick check)
• Before committing or opening a pull request (full pre-commit cycle)
• When a build or test failure appears (clean build pattern)
• Before a release or deploy (release build + bench)
• When updating API docs or dependencies

Best practices

• Run cargo fmt --all -- --check in CI and locally to avoid formatting diffs
• Prefer cargo check for rapid type validation during editing
• Use workspace-wide commands (cargo build/test --workspace) for consistent multi-crate verification
• Enable clippy with -D warnings in pre-commit to enforce zero-warning policy
• Leverage -j and test thread flags to match CI/host CPU for faster runs

Example use cases

• Quick local verification: cargo check && cargo test -- --test-threads=1 after a minor change
• Troubleshooting build cache issues: cargo clean && cargo build --workspace && cargo test --workspace --all-features
• Release preparation: cargo build --release --workspace && cargo test --release --workspace && cargo bench --no-run
• Documentation update: cargo doc --workspace --no-deps --all-features to regenerate API docs