rust-audit

Identify gaps in Rust projects against a 9-dimension quality methodology.

2|1|Updated Feb 15, 2026

Search Tags:#audit #quality #rust #clippy #rustfmt #ci #cargo-audit

Ready to run

npx skills add https://github.com/ondrasek/cc-plugins --skill rust-audit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: rust-audit
Source: https://github.com/ondrasek/cc-plugins/tree/main/plugins/blueprint/skills/rust-audit
Command: npx skills add https://github.com/ondrasek/cc-plugins --skill rust-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Read-only gap analysis comparing a Rust project's current quality setup against the 9-dimension methodology. Use when user says "audit quality", "check coverage gaps", "what's missing", or wants to see how their Rust project measures up before running setup.

Core Features & Use Cases

Read-only gap analysis across the 9 dimensions (edition/MSRV, workspace vs single crate, tooling configs like clippy, rustfmt, deny.toml, and CI coverage).
Provides actionable recommendations to improve setup and align with the methodology.
Suitable as a pre-audit checkpoint before performing rust-audit and setting up tooling.

Quick Start

Run rust-audit on your current Rust project to identify gaps.

Frequently Asked Questions about rust-audit

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

FAQPage Schema

How do I check my Rust project for missing quality and CI configurations?▼

A Rust quality audit compares your project against a 9-dimension methodology to detect missing tooling configurations like clippy, rustfmt, deny.toml, and cargo-audit. It assesses edition detection, MSRV, project structure, and CI coverage, reporting actionable setup guidance to close any gaps.

What is included in a Rust codebase quality audit?▼

A Rust codebase quality audit evaluates edition and MSRV settings, workspace versus single crate structure, tooling configs, and CI coverage. It verifies cargo manifests and checks for the presence of required hooks and CI jobs, providing actionable recommendations to align with the methodology.

Can I run a quality audit on a single crate or does it require a workspace?▼

You can run a quality audit on Rust codebases of any size, including both single crates and workspaces. The analysis evaluates the project structure and tooling configurations regardless of scale to identify quality gaps and provide setup guidance.

How do I find missing clippy and rustfmt configurations in my Rust project?▼

To find missing clippy and rustfmt configurations, run a read-only gap analysis on your Rust project. It verifies tooling settings and checks for the presence of deny.toml and cargo-audit, reporting actionable recommendations to improve your setup and align with the quality methodology.

What does a Rust audit check for in CI coverage and project structure?▼

A Rust audit checks CI coverage by verifying the presence of CI jobs and hooks. It also examines project structure, edition detection, MSRV, and cargo manifests to identify quality gaps and provide actionable setup guidance.

When should I use a read-only Rust quality audit?▼

Use a read-only Rust quality audit as a pre-audit checkpoint when you want to see how your project measures up before running setup. It identifies coverage gaps and missing tooling configurations without modifying your codebase, providing actionable recommendations for improvement.