Quality

Quality checks — what to run and when Use when this capability is needed.

tomevault-io Updated

File contents

Quality

Core Checks (default exit gate)

Six checks run project-wide, in order, once when work is complete. This is the default meaning of "all checks pass."

check-compilecheck-linkcheck-filesizecheck-unitcheck-integrationcheck-complexity

If any fail, fix and re-run only the failing check.

Full Suite (only when explicitly requested)

The core 6 plus 5 deep checks. Run only when the goal or user specifically asks.

check-sanitize · check-tsan · check-valgrind · check-helgrind · check-coverage

Development Inner Loop

After changing a file, run the relevant check with --file=PATH:

  • check-compile --file=PATH after every edit
  • check-unit --file=PATH when a test file exists

Stay in this single-file loop. Do not run project-wide checks during active development.

Build Modes

make BUILD={debug|release|sanitize|tsan|coverage}

CRITICAL: Never run multiple make commands simultaneously — incompatible compiler flags corrupt the build.


Converted and distributed by TomeVault — claim your Tome and manage your conversions.

tomevault-io/skills-registry/tree/main/mgreenly--ikigai--quality commit d1276dbf41

Frequently asked questions

npx skillmds@latest add tomevault-io/quality