doc-rigor

Generate and verify Rust documentation claims against actual code.

1|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/ahrav/Gossip-rs --skill doc-rigor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-rigor
Source: https://github.com/ahrav/Gossip-rs/tree/main/.claude/skills/doc-rigor
Command: npx skills add https://github.com/ahrav/Gossip-rs --skill doc-rigor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the challenge of creating and maintaining high-quality, accurate documentation for Rust code, ensuring that documentation accurately reflects the code's reality and intent.

Core Features & Use Cases

  • Automated Documentation Generation: Writes and improves comments, docstrings, and module-level documentation for Rust code.
  • Automated Verification: Verifies all documentation claims against the actual code using a separate agent to eliminate bias.
  • Use Case: After writing a new Rust module, use this Skill to generate comprehensive documentation and then automatically verify that all explanations of behavior, invariants, and complexity are correct according to the code.

Quick Start

Use the doc-rigor skill to improve documentation for the recently changed Rust files.

Frequently Asked Questions about doc-rigor

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

FAQPage Schema
How do I automatically generate and verify Rust docstrings for my codebase?

You can generate and verify Rust docstrings using a two-agent pipeline that first writes module-level explanations and comments, then validates every claim against code reality to eliminate confirmation bias.

What is the best way to ensure my Rust documentation matches the actual code behavior?

The best way to ensure documentation matches code behavior is automated verification, which checks generated docstrings and comments against the actual Rust code using a separate validation agent.

Can I target specific Rust files for documentation generation and verification?

Yes, you can target specific Rust files by providing targeted file input, allowing you to generate documentation and run verification flags only on recently changed modules.

How does a separate verification agent eliminate confirmation bias in code documentation?

A separate verification agent eliminates confirmation bias by independently validating all documentation claims against the actual code reality, ensuring the generated docstrings accurately reflect behavior and invariants.

Does this documentation tool work with Rust module-level explanations and inline comments?

Yes, this tool works with Rust codebases by generating both inline code comments and module-level explanations, then verifying that all behavioral claims and complexity statements are correct.

When do I need automated documentation verification for my Rust project?

You need automated documentation verification when writing new Rust modules, ensuring that generated docstrings accurately reflect code intent and behavior without manual review overhead.