quality

Run project-wide quality checks including compile, link, and unit tests.

Updated Mar 4, 2026

Search Tags:#automation #testing #build #quality #ci #checks

Ready to run

npx skills add https://github.com/multicam/ikigai-rev --skill quality-multicam

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: quality
Source: https://github.com/multicam/ikigai-rev/tree/main/.claude-i/library/quality
Command: npx skills add https://github.com/multicam/ikigai-rev --skill quality-multicam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates project-wide quality checks to ensure builds and code quality pass.

Core Features & Use Cases

Core Checks (default exit gate): six checks run project-wide in order: check-compile → check-link → check-filesize → check-unit → check-integration → check-complexity.
Full Suite: additional deep checks: check-sanitize, check-tsan, check-valgrind, check-helgrind, check-coverage (triggered on explicit request).
Development Inner Loop: after changing a file, run the relevant check with --file=PATH; stay in a single-file loop.

Quick Start

Run the core quality checks on your codebase to verify the default gate passes.

Frequently Asked Questions about quality

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate CI quality checks for my build environment?▼

You can automate CI quality checks by running the default core six checks sequentially across your project. This requires a configured Make build environment and access to scripts/ for deterministic tasks to verify builds and code quality pass.

What project quality checks are included in the default exit gate?▼

The default exit gate runs six project quality checks in order: check-compile, check-link, check-filesize, check-unit, check-integration, and check-complexity to ensure builds and code quality pass.

Can I run quality checks on a single file during development?▼

Yes, you can run quality checks on a single file by using the --file=PATH flag. This keeps you in a tight development inner loop after changing a file instead of running the full project suite.

How do I trigger deep code quality checks like valgrind and coverage?▼

Deep code quality checks such as check-sanitize, check-tsan, check-valgrind, check-helgrind, and check-coverage are triggered on explicit request rather than running by default during the standard build process.

Do I need Make to run automated project quality checks?▼

Yes, automated project quality checks require a configured Make build environment and access to scripts/ for deterministic tasks to execute the build and code quality verifications properly.

What is the best way to enforce build quality checks locally and in CI workflows?▼

The best way to enforce build quality checks is running the default core six checks as an exit gate in both CI workflows and local development, enabling optional deep checks like check-coverage when explicitly requested.