Enforce a check-first cargo workflow for Rust project validation.
npx skills add https://github.com/lanej/dotfiles --skill rust
Please help me install this Agent Skill. Skill: rust Source: https://github.com/lanej/dotfiles/tree/main/claude/skills/rust Command: npx skills add https://github.com/lanej/dotfiles --skill rust
This Skill addresses the common pain point of slow compilation times in Rust development, especially with optimized release builds. It provides a workflow that prioritizes fast feedback loops, allowing you to iterate quickly and efficiently.
cargo check for rapid verification of code compilation without generating binaries, significantly speeding up your development cycle.cargo run to build debug binaries and execute your code in one command, ideal for testing functionality during active development.cargo clippy to automatically fix and identify code quality and style issues early, ensuring cleaner, more maintainable code.cargo test, cargo check, and cargo clippy --fix for instant feedback, only using cargo run to test execution, and avoiding slow release builds until absolutely necessary.Run the full validation sequence for the current Rust project: tests, compilation check, and clippy.
High-intent search queries and answers about installing and using this skill.
Fast compilation in Rust development uses `cargo check` for rapid verification without generating binaries, followed by `cargo run` for debug builds during iteration. This workflow avoids expensive release builds until necessary, significantly reducing feedback loop time compared to optimized compilation.
Use a check-first workflow: run `cargo check` for compilation validation, `cargo test` for functionality verification, and `cargo clippy` for code quality checks. This approach provides instant feedback on code issues without the overhead of release-optimized builds.
`cargo clippy` identifies and automatically fixes code quality and style issues during development. Running it alongside `cargo check` and `cargo test` in your validation sequence ensures cleaner, more maintainable code before committing changes.
Yes. `cargo check` validates compilation without binaries for fast feedback, while `cargo run` builds debug binaries and executes code in one step. Combining both in your iteration cycle balances rapid validation with functional testing.
Avoid `cargo run` when you only need to verify code compiles or check for lint issues. Use `cargo check` instead for faster feedback. Reserve `cargo run` for testing actual execution behavior; defer release builds until final validation or deployment.
Yes. The check-first workflow with `cargo check`, `cargo test`, and `cargo clippy` scales across iterative development in any Rust codebase size, prioritizing fast feedback loops and avoiding slow release builds during active development cycles.
plurigridAutomate Rust project creation, dependency management, and building with cargo.
d-o-hubSelect distribution channels for Rust crates, WASM npm, and CLI npm artifacts.
po4ykaManage Rust workspace crates, dependencies, and build configurations.
nikomatsakisBuilds custom Rust compiler frontends consuming crate dependency metadata via rustc_driver callbacks.