doc-rigor-verify

Automated Rust documentation verification uses an AI agent to check that all statements in your docs factually match the codebase. It independently reviews generated documentation to prevent drift and ensure accuracy before merging.

Preventing documentation drift in Rust projects requires an automated pipeline that writes and verifies code docs in one pass. By enforcing agent isolation between writing and checking, it eliminates confirmation bias and keeps docs aligned with code.

Generating and verifying Rust code docs in one pass involves orchestrating an end-to-end pipeline. A doc-rigor agent writes or improves documentation for specified files, followed by a separate doc-verify agent checking the output against the actual code.

Yes, you can use an AI agent to write and check documentation for specific Rust files. The pipeline handles file scope resolution to target recently changed modules and presents a combined report of documentation changes and verification findings.

Using separate AI agents for writing and verifying code documentation enforces strict agent isolation. This separation eliminates confirmation bias, ensuring the verification agent rigorously and independently checks the generated docs against the actual codebase.

Automated documentation verification works for recently changed Rust files by resolving file scope and running targeted checks. You can run the pipeline on updated modules to automatically generate accurate documentation and verify it before merging.