What problem does it solve?
This Skill reduces catastrophic C/C++ defects by enforcing disciplined resource ownership, eliminating undefined behavior, and standardizing how native code manages errors, ABI boundaries, and thread safety.
Core Features & Use Cases
- RAII-first ownership enforcement: requires every owned resource to be released by destructors using smart pointers or stack-based RAII, not raw owning pointers.
- Undefined-behavior and correctness guardrails: blocks patterns that commonly lead to silent failure, such as null dereferences, signed-overflow UB, aliasing violations, and data races.
- Native ABI and boundary policies: specifies stable ABI expectations (visibility, extern "C" interface constraints, and semver discipline) and ensures exceptions don’t escape FFI/ABI boundaries.
- Quality evidence baseline: defines sanitizer lanes (ASan/UBSan/TSan/MSan) plus static analysis and fuzzing expectations for critical native code.
Quick Start
Use the cpp-professional-usage skill to review a proposed C++ change for RAII correctness, UB/aliasing risks, ABI boundary safety, and documented thread-safety and error-handling rules.