Rust Development Workflow

Automate cargo build, test, clippy, and fmt across the Miyabi workspace.

Updated Jan 10, 2026
One-click install
npx skills add https://github.com/hiromima/collaborative-canvas --skill rust-development-workflow-hiromima
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Rust Development Workflow
Source: https://github.com/hiromima/collaborative-canvas/tree/main/.claude/skills/rust-development
Command: npx skills add https://github.com/hiromima/collaborative-canvas --skill rust-development-workflow-hiromima

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating a reliable Rust development workflow can be error-prone and time-consuming. This skill automates the process of building, testing, and validating Rust code to ensure consistency across the Miyabi project.

Core Features & Use Cases

  • Complete Rust development pipeline: cargo build, cargo test, cargo clippy, and cargo fmt to maintain quality and speed.
  • Workspace-wide consistency: applies to multi-crate Miyabi workspace, ensuring uniform checks across crates.
  • Use Case: before merging a feature, run the full validation to catch compile errors, failing tests, and formatting issues.

Quick Start

Run the full workflow to build, test, lint, and format the workspace.

Frequently Asked Questions about Rust Development Workflow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Rust workspace builds and tests across multiple crates?

Automating a Rust workspace build and test process involves running cargo build and cargo test across all crates to ensure uniform validation. This workflow coordinates these checks to maintain consistency across multi-crate projects before merging features.

What's the best way to run cargo clippy and cargo fmt for a multi-crate Rust project?

Running cargo clippy and cargo fmt deterministically across a multi-crate Rust project ensures consistent code quality and formatting. A complete development pipeline applies these checks uniformly across the workspace to catch linting and formatting issues before commits.

Does this Rust workflow automation work with any cargo workspace or only specific projects?

This workflow automation is designed for multi-crate Rust projects requiring consistent cargo-based validation, specifically targeting the Miyabi workspace. It applies deterministic steps for building, testing, and linting to ensure uniform checks across crates within that environment.

Why should I run a full Rust validation workflow before merging a feature?

Running a full Rust validation workflow before merging catches compile errors, failing tests, and formatting issues early. Coordinating cargo build, test, clippy, and fmt ensures workspace-wide consistency and prevents error-prone manual checks from reaching the main branch.

How does automated cargo-based error handling work during Rust development validation?

Automated cargo-based validation applies deterministic steps with error handling for build, test, clippy, and fmt operations. This approach systematically validates the Rust workspace, catching and reporting failures consistently across all crates without manual intervention.