review-rust-docs

Audit Rust crate documentation against rust-docs-guidelines and generate a structured report.

6.2k|590|Updated May 5, 2016
One-click install
npx skills add https://github.com/RediSearch/RediSearch --skill review-rust-docs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-rust-docs
Source: https://github.com/RediSearch/RediSearch/tree/main/.skills/review-rust-docs
Command: npx skills add https://github.com/RediSearch/RediSearch --skill review-rust-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps ensure Rust crate documentation meets project standards by systematically auditing docs and identifying non-conformances.

Core Features & Use Cases

  • Audits Rust crate docs against established Rust documentation guidelines.
  • Generates a prioritized report detailing non-conforming sections, with explanations and concrete improvement suggestions.
  • Use Case: A Rust library maintainer runs this Skill to verify that crate docs align with the rust-docs-guidelines before releasing a new version.

Quick Start

Run the skill against the target crate directory, such as the crate source or cargo-generated docs, to initiate the audit and receive a structured report.

Frequently Asked Questions about review-rust-docs

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

FAQPage Schema
How do I audit Rust crate documentation against standards?

Audit Rust crate documentation by running this Skill against your crate directory to systematically check docs conformance against rust-docs-guidelines. It produces a prioritized report identifying non-conforming sections with explanations and concrete improvement suggestions for each gap found.

What documentation gaps does a Rust docs audit typically find?

A Rust documentation audit identifies missing or incomplete doc comments, inconsistent formatting, undocumented public APIs, and sections that diverge from rust-docs-guidelines standards. The Skill reports each non-conformance with specific guidance on how to fix it.

When should I run a documentation review before releasing a Rust crate?

Run a documentation audit before each release to verify that all crate docs align with rust-docs-guidelines. This catches gaps early, ensures consistent quality across modules, and prevents documentation debt from shipping with new versions.

Can I use documentation auditing for Rust libraries and modules together?

Yes, this Skill targets both Rust crates and modules within them. Run it against your crate source or cargo-generated docs directory to audit the entire documentation structure and identify non-conformances at any level.

What's the best way to fix documentation issues found in an audit report?

The audit report provides concrete improvement suggestions for each non-conforming location. Prioritize by severity, apply the suggested fixes to doc comments and markdown files, then re-run the audit to verify conformance before committing changes.

Do I need to set up guidelines before auditing Rust documentation?

No setup required—the Skill reads established rust-docs-guidelines automatically. Simply point it at your crate directory and it generates a structured audit report against those standards without additional configuration.