rust_dev

Run cargo check, fmt, clippy, and test for Rust workspace changes.

1|Updated Sep 18, 2025
One-click install
npx skills add https://github.com/Startti/colmena --skill rust-dev-startti
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rust_dev
Source: https://github.com/Startti/colmena/tree/main/.agent/skills/rust_dev
Command: npx skills add https://github.com/Startti/colmena --skill rust-dev-startti

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents broken Rust builds and inconsistent engineering practices by ensuring every change is planned, compiled, linted, and tested in the correct workspace context.

Core Features & Use Cases

  • Cargo workspace-safe workflow: Uses the proper library directory (src/libs/colmena) for build and test verification to reduce “works on my machine” issues.
  • Quality gates for Rust changes: Requires cargo check/cargo build, along with cargo fmt and cargo clippy to enforce style and catch common mistakes early.
  • Change planning and validation: Demands an implementation_plan.md with exact code references and requires explicit approval before executing non-trivial changes.
  • Use case: Updating a Rust module, adjusting dependencies in the workspace, or changing Cargo.toml requires a consistent plan-to-validate flow with tests updated when APIs change.

Quick Start

Use this skill when you need to implement a non-trivial Rust change by first drafting an implementation_plan.md with the exact file edits, waiting for approval, then running cargo fmt, cargo clippy, and cargo test from src/libs/colmena.

Frequently Asked Questions about rust_dev

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

FAQPage Schema
How do I ensure my Rust Cargo workspace builds reliably after code changes?

Reliable Rust builds require running cargo check, cargo fmt, cargo clippy, and cargo test from the correct workspace directory to validate changes involving Rust source files and Cargo configuration.

What's the best way to update a public API in a Rust module safely?

Updating a public Rust API safely requires drafting an implementation plan with exact modification details, waiting for approval, and mandating cargo test updates for any API changes.

Do I need an implementation plan before modifying Cargo.toml dependencies?

Yes, changing Cargo.toml dependencies requires an implementation_plan.md with exact file edits and explicit approval before executing non-trivial workspace changes.

How does cargo clippy integrate into a Rust development workflow?

Cargo clippy integrates as a quality gate that enforces code style and catches common mistakes early, running alongside cargo check, cargo build, and cargo fmt during Rust source validation.

Why does my Rust build pass locally but fail in the Cargo workspace?

Build failures occur when workspace context is incorrect; using the proper library directory like src/libs/colmena for build and test verification reduces works on my machine issues.