Menu
Quality checks — what to run and when
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Automated quality check loops with escalation and fix sub-agents
JSON-based end-to-end test format, runner, and mock provider
Jujutsu (jj) skill for the ikigai project
How to write effective Ralph goals for Ikigai-driven workflows
Create and manage Ralph goals from Ikigai using the real ralph-pipeline scripts
Create repositories using the real ralph-pipeline repo-create script
| name | quality |
| description | Quality checks — what to run and when |
Six checks run project-wide, in order, once when work is complete. This is the default meaning of "all checks pass."
check-compile → check-link → check-filesize → check-unit → check-integration → check-complexity
If any fail, fix and re-run only the failing check.
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
After changing a file, run the relevant check with --file=PATH:
check-compile --file=PATH after every editcheck-unit --file=PATH when a test file existsStay in this single-file loop. Do not run project-wide checks during active development.
make BUILD={debug|release|sanitize|tsan|coverage}
CRITICAL: Never run multiple make commands simultaneously — incompatible compiler flags corrupt the build.