rust-unsafe

Audit unsafe Rust usage across RIPDPI crates for safety invariants.

58|4|Updated Mar 8, 2026
One-click install
npx skills add https://github.com/po4yka/RIPDPI --skill rust-unsafe-po4yka
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rust-unsafe
Source: https://github.com/po4yka/RIPDPI/tree/main/.claude/skills/rust-unsafe
Command: npx skills add https://github.com/po4yka/RIPDPI --skill rust-unsafe-po4yka

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps maintainers and reviewers enforce safe patterns around unsafe Rust, FFI boundaries, and raw-pointer usage across RIPDPI crates, ensuring codebase integrity.

Core Features & Use Cases

  • Enforce crate-level governance: require #![forbid(unsafe_code)] and lint floors.
  • Audit unsafe blocks, JNI exports, and low-level IO wrappers for safety invariants and documented SAFETY sections.

Quick Start

Run a code review pass focusing on every unsafe boundary and verify SAFETY comments and wrappers, then log and fix any missing invariants.

Frequently Asked Questions about rust-unsafe

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit unsafe Rust blocks during code review?

Auditing unsafe Rust blocks involves identifying FFI boundaries and raw pointer usage, then verifying explicit SAFETY comments and documented invariants exist. The Skill automates these static audit checks during code reviews to enforce strict governance rules.

What is the best way to enforce forbid(unsafe_code) across Rust crates?

Enforcing forbid(unsafe_code) requires applying crate-level governance rules and lint floors. The Skill verifies these attributes during code reviews to maintain safe patterns around unsafe Rust and FFI boundaries across your crates.

How do I verify JNI and Linux IO boundary safety in Rust?

Verifying JNI and Linux IO boundary safety requires auditing low-level IO wrappers and JNI exports for documented invariants. The Skill checks these unsafe boundaries during static audits to ensure proper safety sections are present.

When do I need explicit SAFETY comments for raw pointer manipulation?

Explicit SAFETY comments are required for all unsafe blocks involving raw pointer manipulation. The Skill enforces this during code reviews by verifying documented invariants and proper zeroed usage for plain C structs at FFI boundaries.

Can I use this to check proper zeroed usage for C structs in FFI?

Yes, you can check proper zeroed usage for plain C structs at FFI boundaries. The Skill audits unsafe Rust usage to verify that zeroed struct initialization and other raw pointer manipulations include documented invariants and explicit SAFETY comments.