audit-sans
Skill0 starsChanged 2 days agoMIT-0View on GitHub
Runs unit test suites across dual compilers Clang and GCC, standard library deep hardening, and runtime sanitizers. Use this skill when running sanitizers, checking for memory leaks, data races, or cross-compiler parity.
In this repository5 other files it gives its agents.
- architectSkill
- audit-staticSkill
- featureSkill
- performanceSkill
- resyncSkill
The file
Files
Runtime sanitizers and dual compiler audit workflow
Step 1. AddressSanitizer and LeakSanitizer
cmake --workflow --preset Clang_ASan_Verify
cmake --workflow --preset GNU_ASan_Verify
cmake --workflow --preset Clang_LSan_VerifyStep 2. UndefinedBehaviorSanitizer
cmake --workflow --preset Clang_UBSan_Verify
cmake --workflow --preset GNU_UBSan_VerifyStep 3. ThreadSanitizer
cmake --workflow --preset Clang_TSan_VerifyStep 4. Dual compiler parity and deep standard library hardening
./production_artifacts/build_all.sh custom debug
./production_artifacts/build_all.sh default release
./production_artifacts/build_all.sh custom deepResolve any sanitizer trace, bounds violation, or compiler warning before completing the audit.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.