Audit and review unsafe Rust code with lint floors, Miri checks, and FFI layout rules.
npx skills add https://github.com/po4yka/rust-skills --skill rust-unsafe-po4yka
Please help me install this Agent Skill. Skill: rust-unsafe Source: https://github.com/po4yka/rust-skills/tree/main/skills/rust-unsafe Command: npx skills add https://github.com/po4yka/rust-skills --skill rust-unsafe-po4yka
#![forbid(unsafe_code)] cannot see. - Verification workflow: a tiered check ladder covering clippy lint floors, debug-profile precondition tests, Miri under Stacked Borrows and Tree Borrows, and sanitizer coverage for FFI paths Miri cannot execute. - Triage and pattern references: tables mapping symptoms like E0793, improper_ctypes warnings, and reference fabrication to their causes and fixes, plus detailed references on FFI layout, aliasing models, and audit checklists. - Use Case: When reviewing a pull request that adds an unsafe impl Send or a hand-rolled extern "C" export, the agent runs the inventory, applies the audit checklist, and confirms each unsafe block has a SAFETY comment naming its invariant. ## Quick Start Ask the agent to audit this crate for unsafe code and verify each unsafe block with clippy, debug tests, and Miri.High-intent search queries and answers about installing and using this skill.
Run ripgrep over the crate for `unsafe {`, `unsafe fn`, `unsafe impl`, and unmangled export attributes to map the unsafe surface. Then apply `#![forbid(unsafe_code)]` to crates with no hand-written unsafe and enforce a clippy lint floor on crates that contain it.
Run `cargo +nightly miri test` under the default Stacked Borrows model first, then Tree Borrows as a second opinion. Add `-Zmiri-symbolic-alignment-check` for byte parsers and `-Zmiri-many-seeds` for threaded code, since one seed explores only one schedule.
No, `#![forbid(unsafe_code)]` checks only the crate's own source text, not macro expansions from dependencies. Use `cargo +nightly rustc -- -Zunpretty=expanded` and grep the expansion to find unsafe injected by dependency macros.
Bytes from sockets, files, or FFI callers carry arbitrary alignment, and `ptr::read` requires a pointer aligned for the target type. Use `ptr::read_unaligned`, `zerocopy::FromBytes`, or `from_le_bytes` instead, and test under Miri with symbolic alignment checks.
`mem::zeroed()` is sound only when the exact type's documented contract proves all-zero bytes is a valid value. It is never valid for references, NonNull, NonZero, Box, or function pointers; use `MaybeUninit<T>` when no such proof exists.
Miri cannot execute foreign functions, so tests crossing a real FFI boundary must be marked `#[cfg_attr(miri, ignore)]` and covered with ASan, HWASan, or MTE instead. A `#[cfg(miri)]` stub must dereference every stored pointer or aliasing defects pass undetected.
po4ykaAudit and review unsafe Rust code with lint floors, Miri checks, and FFI layout rules.
po4ykaRun Miri and sanitizers on Rust code to detect undefined behavior and memory errors.
cgfixitVerify Cargo dependencies, security advisories, licenses, and locked versions across Rust crates.
awfixers-stuffGenerate Rust-C FFI bindings with bindgen and cbindgen.