Can it help with FFI bindings?

Absolutely. It provides guidance on using bindgen/cbindgen and ensures correct handling of C-strings and raw pointers at the boundary layers.

Does this skill help with Undefined Behavior (UB)?

Yes, it specifically looks for patterns that lead to UB, such as aliasing violations, alignment issues, and invalid bit patterns in transmutes.

How does it handle raw pointer arithmetic?

It suggests safer alternatives like NonNull and ptr::add, while checking for potential null pointer dereferences before they occur.

Why are SAFETY comments required?

Standard Rust practices require explaining why an unsafe block is sound; this skill enforces those comments to improve code maintainability and auditability.

Unsafe Rust & FFI Checker

Name: Unsafe Rust & FFI Checker
Author: actionbook

byactionbook

•

596

Security & Testing

Audits unsafe Rust code for soundness, memory safety, and proper FFI implementation patterns.

About

⚠️ **Unsafe Rust Checker Loaded** * ^ * /◉\_~^~_/◉\ ⚡/ o \⚡ '_ _' / '-----' \ The Unsafe Rust Checker is a specialized skill for Claude Code designed to review high-stakes Rust code where the compiler's safety guarantees are manually managed. It monitors for unsafe blocks, raw pointer usage, and FFI boundaries to ensure developers follow rigorous soundness requirements. By identifying potential undefined behavior (UB), enforcing mandatory safety documentation, and recommending modern alternatives like MaybeUninit or NonNull, this skill acts as a critical second set of eyes for systems programmers and library authors working at the edge of the language.

Key Features

Detects common memory errors like null pointer dereferences and use-after-free.
Provides guidance on proper FFI integration and C-ABI compatibility.
Suggests modern, safer replacements for deprecated low-level functions.
Validates memory layout, alignment, and bit patterns for raw transformations.
596 GitHub stars
Enforces mandatory SAFETY comments and caller requirement documentation.

Use Cases

Reviewing low-level memory management code for custom data structures.
Auditing external function interfaces (FFI) for correct signatures and safety.
Migrating legacy unsafe code to use modern Rust safety abstractions.

About

Key Features

Detects common memory errors like null pointer dereferences and use-after-free.
Provides guidance on proper FFI integration and C-ABI compatibility.
Suggests modern, safer replacements for deprecated low-level functions.
Validates memory layout, alignment, and bit patterns for raw transformations.
596 GitHub stars
Enforces mandatory SAFETY comments and caller requirement documentation.

Use Cases

Reviewing low-level memory management code for custom data structures.
Auditing external function interfaces (FFI) for correct signatures and safety.
Migrating legacy unsafe code to use modern Rust safety abstractions.