Use when: reviewing C/C++ code for memory safety, undefined behavior, resource leaks,
concurrency bugs, or style issues; debugging segmentation faults, buffer overflows, double free,
or data races; writing new C++ code and following modern best practices (C++11/14/17/20/23);
or when user mentions C, C++, concept, rvalue, move semantics, smart pointer, RAII,
constexpr, clang-tidy, cppcheck, AddressSanitizer, valgrind, or static analysis.
2026-07-15