cpp-core-guidelines-review

To check C++ code for Core Guidelines violations, this Skill runs parallel section-focused reviewers that audit resource management and concurrency safety independently, then aggregates findings into structured markdown reports within a review directory.

Yes, you can exclude directories like third_party during a C++ Core Guidelines code review by clarifying target file scopes and include patterns before execution, ensuring only specified source files are audited.

The best way to review a large C++ change for guideline compliance is to launch dedicated sub-agents in parallel that check bundled sections like functions, classes, and error handling, consolidating per-section findings for engineering follow-up.

No, C++ static analysis for Core Guidelines does not modify reviewed source files; it generates deterministic per-section markdown outputs and an aggregated Summary report in a dedicated review directory without altering the original codebase.

To audit C++ templates and core services for concurrency safety, orchestrate multiple section-focused reviewers in parallel, ensuring constrained per-section review coverage across all relevant Core Guidelines bundles without missing specific rules.