moai-foundation-quality

Assess code changes against TRUST 5 quality principles and MoAI gate enforcement.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/taewook486/Masters_degree --skill moai-foundation-quality-taewook486
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: moai-foundation-quality
Source: https://github.com/taewook486/Masters_degree/tree/main/.claude/skills/moai-foundation-quality
Command: npx skills add https://github.com/taewook486/Masters_degree --skill moai-foundation-quality-taewook486

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Code quality reviews often lack a consistent framework, leading to skipped security checks, unjustified coverage gaps, and subjective assessments. This Skill provides the TRUST 5 quality model (Tested, Readable, Unified, Secured, Trackable) and explains how MoAI enforces it through agents, gate commands, and a 3-level harness. ## Core Features & Use Cases - TRUST 5 Assessment Checklists: Per-principle evaluation questions with a justified-skip guard so no dimension is silently ignored. - Quality Gate Guidance: Explains how /moai gate runs lint, format, type-check, and tests in parallel across 16 auto-detected language toolchains. - sync-auditor Scoring Model: Documents the 4-dimension harmonic-mean scoring (Functionality, Security, Craft, Consistency) used at the thorough harness level. - Use Case: Before merging an authentication endpoint change, walk all five TRUST 5 dimensions, triage /moai gate findings by severity, and verify coverage meets the 85% threshold with actual command output. ## Quick Start Ask the assistant to assess the current code change against the TRUST 5 quality principles and triage any gate findings.

Frequently Asked Questions about moai-foundation-quality

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

FAQPage Schema
How do I apply TRUST 5 principles to a code review?▼

Evaluate each change against five dimensions: Tested, Readable, Unified, Secured, and Trackable. Treat each as an assessment question with a checklist, and if a dimension does not apply, state the justification explicitly rather than skipping it silently.

What does the /moai gate command check?▼

The /moai gate command runs lint, format, type-check, and tests in parallel as a pre-commit quality gate. It auto-detects the project language and runs the appropriate toolchain, skipping tools that are not installed.

How does sync-auditor score code quality?▼

sync-auditor scores four dimensions: Functionality, Security, Craft, and Consistency. The overall score is the harmonic mean rather than the average, so a single weak dimension like security drags the result down and blocks a pass.

What coverage threshold does the quality gate require?▼

The default package-level coverage threshold is 85 percent, with 90 percent or higher required for critical packages. A coverage figure is only valid when the coverage command was actually run and its output observed in the current session.

When should I use the thorough harness level instead of standard?▼

Use the thorough level for large SPECs, high-risk changes, or security-sensitive work, since it adds full sync-auditor 4-dimension scoring on top of the standard checks. Minimal and standard levels rely on gate commands alone.

How should linter false positives be handled?▼

Suppress false positives per-line with an inline comment stating the reason. Disabling a linter rule globally is prohibited because it hides real issues and trains the team to ignore warnings.