القائمة
Use when about to claim a fix compiles, a bug is resolved, or a change is complete - requires actually building before asserting success
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
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 editing C/C++ files, before claiming edits are complete, or when tempted to manually adjust indentation, spacing, brace placement, or include ordering
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
استنادا إلى تصنيف SOC المهني
| name | verify-build |
| description | Use when about to claim a fix compiles, a bug is resolved, or a change is complete - requires actually building before asserting success |
A change that looks correct can silently break a different compilation unit. Do not claim a fix is done until you have read zero-error build output.
.cpp files across different projects. A change to SSEUtils.h can break PhysicsRTTR.cpp, BVH.cpp, and benchmarks simultaneously.See memory reference_build.md for full commands.
# Generate solution
premake5 vs2022
# Build a specific project (Debug)
MSBuild GLEngine.sln /t:<ProjectName> /p:Configuration=Debug /p:Platform=x64
# Build everything
MSBuild GLEngine.sln /p:Configuration=Debug /p:Platform=x64
Editing a header and only mentally verifying the one .cpp you were looking at. The compiler sees every translation unit that includes the header — they all must compile.
Red flag: "The change looks correct" — looking is not building.