quality

Sequence Makefile quality checks from compile through complexity.

Updated Jun 3, 2026
One-click install
npx skills add https://github.com/mgreenly/ikigai --skill quality-mgreenly
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: quality
Source: https://github.com/mgreenly/ikigai/tree/main/.claude/library/quality
Command: npx skills add https://github.com/mgreenly/ikigai --skill quality-mgreenly

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quality checks are essential but can be manual and error-prone; this Skill orchestrates and standardizes the repository-wide quality gate, ensuring consistent validation of code before release.

Core Features & Use Cases

  • Core gate sequence: check-compile → check-link → check-filesize → check-unit → check-integration → check-complexity.
  • Flexible: run default core checks or full suite including sanitize, tsan, valgrind, helgrind, and coverage.
  • Development loop: supports iterative fixes during local development with guided re-run.

Quick Start

Run the default quality gate to verify compilation, linking, file size, unit checks, integration, and complexity.

Frequently Asked Questions about quality

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

FAQPage Schema
How do I automate a multi-stage repository quality gate in CI?

Automate a repository quality gate by sequencing core checks from compile through complexity. This coordinates check-compile, check-link, check-filesize, check-unit, check-integration, and check-complexity to validate code before release.

What checks are included in a standard code quality gate sequence?

A standard code quality gate sequence includes check-compile, check-link, check-filesize, check-unit, check-integration, and check-complexity. These stages ensure consistent validation of compilation, linking, file size, unit tests, integration tests, and code complexity.

Do I need a Makefile build system to run automated quality checks?

Yes, you need a defined Makefile-based build system to run these automated quality checks. The system requires specific Makefile targets for check-compile, check-link, check-filesize, check-unit, check-integration, and check-complexity.

Can I run extended code checks like valgrind and coverage locally?

Yes, you can run extended code checks locally by using the full suite option. This includes additional checks for sanitize, tsan, valgrind, helgrind, and coverage beyond the default core quality gate sequence.

How do I handle iterative fixes during local development quality checks?

Handle iterative fixes during local development quality checks using the guided re-run development loop. This supports running the default core checks repeatedly to verify fixes before submitting code.