What problem does it solve? C++ defects like null dereferences, use-after-free, data races, and include hygiene issues are easy to miss in review. This Skill explains how to run the repository's full static-analysis and sanitizer stack locally, interpret each tool's output, and satisfy the merge-blocking quality gates before opening a pull request. ## Core Features & Use Cases - Full analyzer orchestration: Run clang-format, clang-tidy, scan-build, cppcheck, and IWYU across all translation units via RunQuality.sh, with a --fast mode that skips only scan-build. - Sanitizer workflows: Build and test with ASan/UBSan/LSan (dev-sanitize preset) and TSan (dev-tsan preset) matching the CI sanitizer matrix. - Finding interpretation: Guidance for reading clang-tidy diagnostics, scan-build HTML reports, sanitizer stack traces, and IWYU add/remove suggestions, plus rules for narrow NOLINT suppressions. - Use Case: Before pushing a C++ change, run ./RunQuality.sh --base origin/main --head HEAD, fix any clang-tidy or cppcheck findings, and confirm the sanitizer ctest presets pass so CI does not reject the PR. ## Quick Start Ask the assistant to run the full static-analysis and sanitizer checks on your current C++ branch and explain any findings before you open the pull request.
