What problem does it solve? Rust code with unsafe blocks and FFI can contain undefined behavior that the compiler cannot catch, and developers struggle to choose between Miri, ASan, TSan, MSan, HWASan, and MTE, configure their flags correctly, and interpret their reports. ## Core Features & Use Cases - Tool Selection and Triage: Maps each bug class (aliasing violations, use-after-free, data races, uninitialized reads) to the correct tool, with failure-triage tables matching Miri and ASan error messages to probable causes and fixes. - Concrete Run Commands: Provides copy-paste commands for host sanitizers with -Zbuild-std, Miri jobs with MIRIFLAGS like -Zmiri-strict-provenance and -Zmiri-tree-borrows, plus Android HWASan/MTE and iOS Xcode sanitizer setups. - FFI Stubbing Guidance: Shows how to write #[cfg(miri)] stubs that preserve signatures and pointer semantics so Miri still detects Box-plus-FFI aliasing defects. - Use Case: A pull request adds raw-pointer parsing code. Use this Skill to gate it with cargo +nightly miri test under Stacked Borrows and symbolic alignment checks, add a Tree Borrows run as extra evidence, and cover the FFI paths Miri skips with an ASan job in CI. ## Quick Start Ask the agent to set up a Miri and AddressSanitizer CI pipeline for a Rust crate that contains unsafe code and a C dependency.