codebase-audit-reviewer

To fact-check documentation against source code, audit README.md, docs, and facts.toml entries by inspecting source files, function signatures, and public APIs. This skill enforces source-verification and consistency checks to output precise corrections for in-place fixes.

Auditing codebase documentation for multi-crate projects requires consistency and completeness checks across all crates. This skill verifies references to functions, types, and modules across single-crate and multi-crate projects, producing actionable corrections for doc claims during drafting or post-release reviews.

Yes, you can verify README accuracy by inspecting function signatures and type definitions. This skill validates references to functions, types, and modules in READMEs and code-derived docs to ensure they reflect the current source code behavior and reduce mismatches.

To start a codebase audit in executor mode, include the executor skill-mode tag in your prompt. This initiates the source-verification process to audit codebase documentation and generate actionable corrections for in-place fixes.

Code-derived documentation mismatches current source code when references to functions, types, and modules are not updated during drafting or post-release. This skill performs completeness audits and consistency checks to identify and correct these documentation mismatches.

A facts.toml file is one of the entries this skill audits for alignment with the source code. While it focuses on verifying README.md, docs, and facts.toml entries, the core requirement is having source files and documentation outputs ready for source-verification and consistency checks.