kani-proof-audit

Audit Kani formal verification proofs in Rust codebases for coverage gaps.

Updated Apr 3, 2026

Search Tags:#testing #security #audit #rust #formal-verification #kani

Ready to run

npx skills add https://github.com/strawgate/agent-skills --skill kani-proof-audit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: kani-proof-audit
Source: https://github.com/strawgate/agent-skills/tree/main/kani-proof-audit
Command: npx skills add https://github.com/strawgate/agent-skills --skill kani-proof-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the difficulty of maintaining comprehensive formal verification in Rust projects by cataloging existing Kani proofs and identifying critical coverage gaps in the codebase.

Core Features & Use Cases

Proof Cataloging: Automatically scans the codebase to map all Kani proof harnesses, function contracts, and bolero tests.
Gap Analysis: Classifies unverified public APIs by severity to prioritize security-critical verification tasks.
Use Case: Use this skill to audit a high-assurance Rust crate, ensuring that all public functions are covered by either exhaustive Kani proofs or robust proptest oracles.

Quick Start

Run the kani-proof-audit skill to generate a comprehensive verification report for the current repository.

Frequently Asked Questions about kani-proof-audit

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

FAQPage Schema

How do I audit Kani formal verification proofs in a Rust codebase?▼

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.

What is the best way to identify unverified public APIs in a Rust crate?▼

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.

Do I need shell access to verify Rust formal proof coverage?▼

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.

How does a formal verification audit handle proof harnesses and function contracts?▼

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.

Can I use this audit to check if my Rust public functions have exhaustive Kani proofs?▼

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.

When should I not rely on Kani proofs for Rust formal verification?▼

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.