القائمة
Use when editing C/C++ files, before claiming edits are complete, or when tempted to manually adjust indentation, spacing, brace placement, or include ordering
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when asked to run the Google Benchmark suite, measure performance, or compare two benchmark runs (before/after an optimization) on this Windows/MSVC project
Use when asked to measure, report, or investigate test code coverage on Windows/MSVC builds - requires OpenCppCoverage and an already-built test binary
Use ONLY when the user explicitly requests a Natvis visualizer for a specific type - never generate unprompted
Use when about to claim a fix compiles, a bug is resolved, or a change is complete - requires actually building before asserting success
| name | clang-format |
| description | Use when editing C/C++ files, before claiming edits are complete, or when tempted to manually adjust indentation, spacing, brace placement, or include ordering |
Never manually reformat C/C++ code. Always delegate formatting to clang-format. Each module has its own .clang-format — clang-format picks up the nearest one automatically.
After editing any C/C++ file, run:
clang-format -i <file>
For multiple files:
clang-format -i File1.cpp File1.h
.cpp, .h, or .inl files#includesRunning clang-format on the whole directory when you only edited one file — this risks reformatting vendor or generated code. Format only the files you touched.