rustdoc — community rustdoc, community, ide skills

v1.0.0

About this Skill

Perfect for Rust Development Agents needing high-quality documentation generation. Rust documentation conventions (RFC 1574). Apply when writing doc comments on public Rust items. Covers summary sentences, section headings, type references, and examples.

uwu uwu
[0]
[0]
Updated: 3/12/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 7/11

This page remains useful for operators, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution Locale and body language aligned
Review Score
7/11
Quality Score
48
Canonical Locale
en
Detected Body Locale
en

Perfect for Rust Development Agents needing high-quality documentation generation. Rust documentation conventions (RFC 1574). Apply when writing doc comments on public Rust items. Covers summary sentences, section headings, type references, and examples.

Core Value

Empowers agents to write proper documentation for Rust code following Rust Documentation Conventions (RFC 1574), utilizing guidelines for doc comments and summary sentences, and adhering to specific formatting rules for public Rust items.

Ideal Agent Persona

Perfect for Rust Development Agents needing high-quality documentation generation.

Capabilities Granted for rustdoc

Generating documentation for Rust crates
Validating doc comments against RFC 1574
Automating documentation updates for Rust projects

! Prerequisites & Limits

  • Requires Rust codebase
  • Adherence to Rust Documentation Conventions (RFC 1574)

Why this page is reference-only

  • - The underlying skill quality score is below the review floor.

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is rustdoc?

Perfect for Rust Development Agents needing high-quality documentation generation. Rust documentation conventions (RFC 1574). Apply when writing doc comments on public Rust items. Covers summary sentences, section headings, type references, and examples.

How do I install rustdoc?

Run the command: npx killer-skills add uwu/flora/rustdoc. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for rustdoc?

Key use cases include: Generating documentation for Rust crates, Validating doc comments against RFC 1574, Automating documentation updates for Rust projects.

Which IDEs are compatible with rustdoc?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for rustdoc?

Requires Rust codebase. Adherence to Rust Documentation Conventions (RFC 1574).

How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add uwu/flora/rustdoc. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use rustdoc immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

rustdoc

Install rustdoc, an AI agent skill for AI agent workflows and automation. Review the use cases, limitations, and setup path before rollout.

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

Rust Documentation Conventions (RFC 1574)

Apply these rules when writing doc comments (///) on public Rust items.

Summary Sentence

Every doc comment starts with a single-line summary sentence.

rust
1// DO: third person singular present indicative, ends with period 2/// Returns the length of the string. 3/// Creates a new instance with default settings. 4/// Parses the input and returns the result. 5 6// DON'T: imperative, missing period, or verbose 7/// Return the length of the string 8/// This function creates a new instance with default settings. 9/// Use this to parse the input and get the result back.

Comment Style

Use line comments, not block comments.

rust
1// DO 2/// Summary sentence here. 3/// 4/// More details if needed. 5 6// DON'T 7/** 8 * Summary sentence here. 9 * 10 * More details if needed. 11 */

Use //! only for crate-level and module-level docs at the top of the file.

Section Headings

Use these exact headings (always plural):

rust
1/// Summary sentence. 2/// 3/// # Examples 4/// 5/// # Panics 6/// 7/// # Errors 8/// 9/// # Safety 10/// 11/// # Aborts 12/// 13/// # Undefined Behavior
rust
1// DO 2/// # Examples 3 4// DON'T 5/// # Example 6/// ## Examples 7/// **Examples:**

Type References

Use full generic forms and link with reference-style markdown.

rust
1// DO 2/// Returns [`Option<T>`] if the value exists. 3/// 4/// [`Option<T>`]: std::option::Option 5 6// DON'T 7/// Returns `Option` if the value exists. 8/// Returns an optional value.

Examples

Every public item should have examples showing usage.

rust
1/// Adds two numbers together. 2/// 3/// # Examples 4/// 5/// ``` 6/// let result = my_crate::add(2, 3); 7/// assert_eq!(result, 5); 8/// ``` 9pub fn add(a: i32, b: i32) -> i32 { 10 a + b 11}

For multiple patterns:

rust
1/// Parses a string into a number. 2/// 3/// # Examples 4/// 5/// Basic usage: 6/// 7/// ``` 8/// let n: i32 = my_crate::parse("42").unwrap(); 9/// assert_eq!(n, 42); 10/// ``` 11/// 12/// Handling errors: 13/// 14/// ``` 15/// let result = my_crate::parse::<i32>("not a number"); 16/// assert!(result.is_err()); 17/// ```

Errors Section

Document what errors can be returned and when.

rust
1/// Reads a file from disk. 2/// 3/// # Errors 4/// 5/// Returns [`io::Error`] if the file does not exist or cannot be read. 6/// 7/// [`io::Error`]: std::io::Error

Panics Section

Document conditions that cause panics.

rust
1/// Divides two numbers. 2/// 3/// # Panics 4/// 5/// Panics if `divisor` is zero. 6pub fn divide(dividend: i32, divisor: i32) -> i32 { 7 assert!(divisor != 0, "divisor must not be zero"); 8 dividend / divisor 9}

Safety Section

Required for unsafe functions.

rust
1/// Dereferences a raw pointer. 2/// 3/// # Safety 4/// 5/// The pointer must be non-null and properly aligned. 6/// The pointed-to memory must be valid for the lifetime `'a`. 7pub unsafe fn deref<'a, T>(ptr: *const T) -> &'a T { 8 &*ptr 9}

Module vs Type Docs

  • Module docs (//!): high-level summaries, when to use this module
  • Type docs (///): comprehensive, self-contained

Some duplication is acceptable.

Language

Use American English spelling: "color" not "colour", "serialize" not "serialise".

Related Skills

Looking for an alternative to rustdoc or another community skill for your workflow? Explore these related open-source skills.

View All

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

333.8k
0
AI

widget-generator

Logo of f
f

Generate customizable widget plugins for the prompts.chat feed system

149.6k
0
AI

flags

Logo of vercel
vercel

The React Framework

138.4k
0
Browser

pr-review

Logo of pytorch
pytorch

Tensors and Dynamic neural networks in Python with strong GPU acceleration

98.6k
0
Developer