What problem does it solve?
It prevents C++ code from drifting into unsafe, inconsistent, or unreviewable implementations by forcing a precise documentation-first specification for C++ projects.
Core Features & Use Cases
- Version & feature constraints: Requires the spec to prefer modern C++ (C++17/20/23), use
constexpr, and document auto and structured bindings usage.
- Formatting as a non-negotiable gate: Enforces
clang-format so style debates never block delivery.
- Memory safety & ownership documentation: Mandates RAII, clearly defines resource ownership, and bans raw
new/delete in the spec.
- Reviewable error handling & naming: Requires specific guidance for exceptions vs.
std::optional/std::expected, plus consistent naming conventions.
- Build/test and review checklists: Provides concrete commands for diagnostics/rebuild/tests and a structured
/code-review checklist for security, concurrency, and quality.
Quick Start
Use the C++ skill to review an existing pull request by instructing your agent to produce (and then verify) a C++ documentation spec covering version, formatting, RAII ownership, error handling, and the required review checklist.