agentleFS
Sign inStart free
JeffKarlingJeffKarling/Anvil/.agents/skills/audit-static/SKILL.md

audit-static

Skill0 starsChanged 2 days agoMIT-0View on GitHub

Runs compile-time static analysis, Clang-Tidy checks, Cppcheck scans, and Include-What-You-Use header hygiene. Use this skill when running static analysis, checking code quality, or auditing header includes.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run Cppcheck in advisory mode against compile_commands.json without modifying CMake cache flags.

    line 23
  2. Distinctive:

    Run Include-What-You-Use to audit public contract hygiene and forward declaration opportunities.

    line 33

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Static analysis and header hygiene workflow

Step 1. Clang-Tidy analysis

Execute Clang-Tidy under the dedicated analysis preset.

cmake --preset Clang_Tidy
cmake --build --preset Clang_Tidy

Category A defects halt the build automatically. Log intentional Category B situational exceptions in production_artifacts/clang_tidy_state.md.

Step 2. Advisory Cppcheck scan

Run Cppcheck in advisory mode against compile_commands.json without modifying CMake cache flags.

python3 .agents/skills/audit-static/scripts/scan_advisory.py --cppcheck

Findings are parsed into structured records in production_artifacts/cppcheck_report.json and converted into manifest refactor tickets.

Step 3. Advisory Include-What-You-Use scan

Run Include-What-You-Use to audit public contract hygiene and forward declaration opportunities.

python3 .agents/skills/audit-static/scripts/scan_advisory.py --iwyu
grep -rn '#include "' targets/

Suggestions are saved to production_artifacts/iwyu_report.json and converted into contract_insulation refactor candidates. Ensure all target headers use angle brackets.

Step 4. Manifest synchronization and multi compiler verification

Synchronize manifest.json with newly generated scanner candidates and verify dual compiler builds.

python3 .agents/skills/architect/scripts/sync_manifest.py --check
cmake --build --preset GNU_Custom_Debug
cmake --build --preset Clang_Custom_Debug

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free