Analyze Rust unsafe code blocks and FFI interactions for soundness.
npx skills add https://github.com/huiali/rust-skills --skill rust-unsafe-huiali
Please help me install this Agent Skill. Skill: rust-unsafe Source: https://github.com/huiali/rust-skills/tree/main/.codex/skills/rust-unsafe Command: npx skills add https://github.com/huiali/rust-skills --skill rust-unsafe-huiali
This Skill addresses the critical need for ensuring the safety and correctness of unsafe Rust code, which bypasses Rust's standard memory safety guarantees. It helps developers identify when unsafe is necessary, how to use it minimally, and how to rigorously verify its soundness.
unsafe blocks, ensuring they adhere to Rust's safety invariants.unsafe code within safe abstractions to protect the rest of the codebase.Use the rust-unsafe skill to review the provided unsafe Rust code snippet for soundness issues.
High-intent search queries and answers about installing and using this skill.
To verify unsafe Rust soundness, review unsafe blocks against Rust safety invariants, checking pointer validity, memory aliasing rules, and panic safety across ABI boundaries. This enforces strict SAFETY comment documentation to prevent undefined behavior.
Interfacing Rust with a C library safely requires writing a safe Rust wrapper around the external functions to encapsulate the unsafe operations. You must manage raw pointer validity, verify memory layout, and handle errors across the FFI boundary.
Minimizing unsafe surface area involves encapsulating unsafe code within safe abstractions to protect the rest of the codebase. By restricting unsafe operations to a minimal, contained wrapper, you maintain standard memory safety guarantees for downstream consumers.
Miri is utilized to detect undefined behavior in Rust unsafe blocks during validation. Running Miri helps identify issues with pointer validity and memory aliasing rules, ensuring your unsafe code adheres to strict safety invariants before deployment.
You need to write SAFETY comments for Rust unsafe code whenever encapsulating unsafe operations within safe abstractions. This strict documentation explains how the code upholds safety invariants, ensuring pointer validity and panic safety across ABI boundaries.
Rust unsafe code review explicitly handles panic safety across ABI boundaries. It validates that panics do not cross FFI boundaries improperly, ensuring memory safety and preventing undefined behavior when interacting with external C libraries.
d-o-hubDiagnose runtime issues in Rust async code with Tokio, Turso, and redb.
po4ykaDetect undefined behavior in Rust with Miri and sanitizers.
laurigatesAssist with modern Rust development using cargo, rustc, clippy, and rustfmt.
Avi977Detect runtime memory errors in fuzzed C/C++ code with AddressSanitizer.