testing

Run cargo test, fmt, and clippy checks on Rust projects.

1|Updated Jan 24, 2026
One-click install
npx skills add https://github.com/dataroadinc/rhusky --skill testing-dataroadinc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testing
Source: https://github.com/dataroadinc/rhusky/tree/main/.claude/skills/testing
Command: npx skills add https://github.com/dataroadinc/rhusky --skill testing-dataroadinc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams ensure Rust code quality by running tests, formatting checks, and linting across the codebase, catching issues early before they reach production.

Core Features & Use Cases

  • Running Tests: Execute all tests, a specific test, or tests with verbose output to verify correctness.
  • Formatting: Enforce consistent code style using nightly toolchains.
  • Linting with Clippy: Run Clippy with strict settings to catch warnings and missing docs.
  • Full Check Workflow: Chain formatting, linting, and testing into a single quality gate.

Quick Start

Run the full quality workflow for your Rust project by formatting, linting, and testing your Rust code.

Frequently Asked Questions about testing

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

FAQPage Schema
How do I run Rust code formatting, linting, and tests in a single CI workflow?

Run a full Rust quality workflow by chaining cargo +nightly fmt, cargo +nightly clippy, and cargo test to enforce code style and verify compilation success in one step.

What is the best way to automate Clippy linting with strict settings in Rust?

Automate Clippy linting using nightly toolchains to catch warnings and missing docs, applying strict quality gates to Rust projects during development and CI workflows.

Do I need a nightly Rust toolchain to enforce formatting and linting checks?

Yes, enforcing consistent code style and running Clippy with strict settings requires nightly toolchains, executing commands like cargo +nightly fmt and cargo +nightly clippy.

Can I run a specific Rust test with verbose output instead of the full test suite?

Yes, you can execute all tests, a specific test, or tests with verbose output to verify correctness, allowing targeted checks before applying the full quality gate.

Why does my Rust CI workflow fail when missing docs are detected by Clippy?

Clippy with strict settings catches missing docs as warnings, failing the CI quality gate to ensure code style compliance and documentation coverage across the codebase.