rustfeed-quality

Automate Rust formatting, linting, tests, and documentation checks with cargo commands.

Updated Dec 25, 2025
One-click install
npx skills add https://github.com/ereferen/rustfeed --skill rustfeed-quality
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rustfeed-quality
Source: https://github.com/ereferen/rustfeed/tree/main/.claude/skills/rustfeed-quality
Command: npx skills add https://github.com/ereferen/rustfeed --skill rustfeed-quality

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates Rust project quality checks to ensure formatting, linting, tests, and documentation are maintained automatically, reducing CI failures and review time.

Core Features & Use Cases

  • Format validation: run cargo fmt --check to ensure code is formatted according to Rust standards.
  • Lint validation: run cargo clippy --all-targets --all-features -- -D warnings to catch common mistakes and best-practice issues.
  • Test & docs validation: run cargo test and cargo doc --no-deps to verify tests pass and documentation builds cleanly.
  • Use Case: before merging a PR, run rustfeed-quality to lock in code quality and prevent regressions.

Quick Start

Run the rustfeed-quality skill on your Rust project to verify formatting, linting, tests, and docs.

Frequently Asked Questions about rustfeed-quality

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

FAQPage Schema
How do I automate Rust code quality checks before a commit?

Automate Rust code quality checks before a commit by running cargo fmt --check, cargo clippy with warnings denied, cargo test, and cargo doc. This prevents CI failures and locks in formatting, linting, tests, and documentation validation.

What does cargo clippy --all-targets --all-features -- -D warnings do for Rust projects?

Running cargo clippy --all-targets --all-features -- -D warnings performs lint validation across all targets and features in a Rust project. It catches common mistakes and ensures best-practice issues fail the build when warnings are detected.

Can I run Rust formatting and documentation checks across monorepos?

Yes, you can run Rust formatting and documentation checks across monorepos. The automated checks target Rust crates, monorepos, or individual projects to verify formatting standards and ensure documentation builds cleanly using cargo doc --no-deps.

What is the best way to prevent CI failures in Rust PR reviews?

The best way to prevent CI failures in Rust PR reviews is running automated pre-commit quality checks. Validating formatting, clippy lints, tests, and documentation locally before merging prevents regressions and reduces overall review time.

How do I verify Rust documentation builds without dependencies?

Verify Rust documentation builds without dependencies by running cargo doc --no-deps. This validates that your project documentation generates cleanly and passes pre-merge quality checks without including external crate documentation.