lang-rust-docs-dev

Standardize Rust documentation with rustdoc conventions and intra-doc links.

Updated Jan 28, 2026
One-click install
npx skills add https://github.com/aRustyDev/git-atomic --skill lang-rust-docs-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lang-rust-docs-dev
Source: https://github.com/aRustyDev/git-atomic/tree/main/.claude/skills/lang-rust-docs-dev
Command: npx skills add https://github.com/aRustyDev/git-atomic --skill lang-rust-docs-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides guidelines for writing high-quality Rust documentation following rustdoc conventions, including inline docs, intra-doc links, error sections, and crate API references for the HASH codebase.

Core Features & Use Cases

  • Guidelines for rustdoc, doc comments, intra-doc links
  • Examples aligned with cargo doc outputs
  • References to existing docs in the repository

Quick Start

Inspect the current Rust documentation patterns, generate docs with cargo doc, and apply the repository's documentation references to update code comments.

Frequently Asked Questions about lang-rust-docs-dev

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

FAQPage Schema
How do I write Rust documentation that follows rustdoc conventions for modules and crate APIs?

Rust documentation for modules and crate APIs should use inline doc comments, intra-doc links, and proper Errors sections. This Skill enforces those rustdoc standards to ensure documentation consistency across the HASH codebase.

How do I use intra-doc links in Rust doc comments to reference types and traits?

Intra-doc links in Rust doc comments connect your documentation to specific types and traits automatically. This Skill provides guidelines for applying intra-doc links and reference patterns correctly across your crate APIs.

What is the best way to document Errors sections in Rust libraries?

Documenting Errors sections in Rust libraries requires detailing failure conditions within your doc comments. This Skill enforces proper Errors section standards, ensuring crate APIs clearly communicate potential failures to users.

How do I generate and validate Rust documentation using cargo doc?

You can generate Rust documentation using cargo doc, then apply repository references to update code comments. This Skill aligns your inline docs and examples with cargo doc outputs to maintain quality standards.

Can I apply these Rust documentation standards to libraries outside the HASH codebase?

These Rust documentation standards target the HASH codebase specifically, guiding modules, types, traits, and crate APIs. The rules focus on intra-doc links and error sections described in the repository references.

Why do my Rust doc comments show inconsistent formatting across different crate APIs?

Inconsistent Rust doc comments occur when documentation lacks enforced standards for intra-doc links and error sections. This Skill solves that problem by detailing rustdoc conventions to improve consistency across the codebase.