kani-proof-audit

To audit Kani formal verification proofs, the skill scans Rust crate structures to catalog proof harnesses, function contracts, and bolero tests, producing a report that identifies coverage gaps and verifies proof integrity.

The best way to identify unverified public APIs is to run a gap analysis that classifies unverified public APIs by severity, helping prioritize security-critical verification tasks for your Rust crate.

Yes, you need shell access and grep to verify Rust formal proof coverage, as the skill requires these tools to traverse crate structures and evaluate proof tiering against project-specific documentation.

A formal verification audit handles proof harnesses and function contracts by automatically scanning the codebase to map all existing Kani proofs and evaluate their tiering against project documentation.

Yes, you can use this audit to check if your Rust public functions have exhaustive Kani proofs or robust proptest oracles by analyzing the public API surfaces and cataloging existing verification coverage.

You should not rely solely on Kani proofs when the audit reveals critical coverage gaps, indicating that public functions lack exhaustive proofs or robust proptest oracles for comprehensive verification.