low-level-systems-extension

To review C or C++ code for memory safety, the Skill evaluates explicit ownership, lifetime tracking, and resource cleanup to detect exploitable memory corruption and undefined behavior risks. It returns blocking or non-blocking decisions based on these findings.

To prevent ABI breakage when modifying native libraries, the Skill assesses ABI and FFI compatibility expectations, including versioning requirements. It ensures your low-level systems changes maintain stable interfaces across kernel, driver, and runtime environments.

To verify lock ordering and concurrency correctness in unsafe Rust, the Skill reviews documented lock ordering, atomic memory ordering, and race mitigation strategies. It enforces sanitizer and tooling expectations to prevent deadlocks and data races.

Yes, this supports seccomp syscall minimization and O_CLOEXEC hygiene checks by assessing your syscall surface and file descriptor handling. It enforces overflow-checked security arithmetic and safe resource boundary adjustments.

The best way to validate performance profiling for systems code changes is using the Skill's profiling-first performance validation requirement. It assesses proposed low-level native changes and requires concrete performance evidence before code ships.

Yes, you can use this for kernel driver and networking boundary adjustments as it evaluates syscall and sandbox boundary modifications. It ensures correctness and security in critical low-level systems work across C, C++, and Rust.