Check whether the installed kverus-common skill stays synchronized with the local Verus guide under database/verified/code/tools/verus/source/docs/guide/src. Use when validating kverus-common after guide updates, before committing skill changes, or when checking for stale guide-derived references and missing source…
Shared Rust/Verus proof references and Asterinas/VOSTD project practices for other KVerus skills. Use when Codex is repairing Verus failures, adding specifications, migrating Rust, classifying axioms or trusted boundaries, modeling external APIs, cleaning proof scaffolding, or working with Asterinas/VOSTD verification…
Evaluate current unstaged spec modifications for semantic quality and intent preservation, then score the modification out of 10. Use when reviewing spec edits before staging or committing.
Fix Verus verification errors by iterating minimal proof-preserving edits until verification succeeds. Use with an explicit target and verification command, or automatically discover the command and locate the target from fresh diagnostics when either input is unavailable.
Convert a Rust target into minimally modified Verus-compatible code using an explicit verification command. Use when migrating a specific file and iterating until the verification command succeeds.
Final cleanup for Verus proof changes: refresh review rules, verify with a user-provided command, delegate redundant proof-assert removal to kverus-strip, re-verify, format, and run local checks. Use after proof-sensitive KVerus skill work or before finalizing Verus changes.
Review uncommitted or recent Verus code changes for exec-code modifications, unnecessary == introductions, and verification issues. Use before committing to catch regressions in executable semantics, set reasoning, and proof quality.
Run the full Rust-to-Verus pipeline (migrate → spec → fix → eval → semantic audit → postprocess) in one command. Use when converting Rust code to verified Verus code end-to-end.
Compare original Rust source folders against migrated Verus code folders, identify executable-code differences that may change runtime semantics, and write per-file audit reports to an output folder. Use when checking whether Rust-to-Verus rewriting preserved executable behavior rather than merely verifying…
Add Verus specification scaffolding to an entry target file while preserving executable behavior. Use when you want stronger proof-ready specs (requires, ensures, invariants, decreases, recommends, spec helpers) without fully finishing proofs.
Aggressively strip redundant proof code from a Verus codebase while keeping verification passing. Use when you want to slim down Verus proof bloat, simplify redundant proof asserts, or run postprocess cleanup without breaking verification.