What problem does it solve?
Harness specialists authoring or reviewing moai-adk-go code need a single authoritative reference for quality gates, test isolation rules, and hardcoding-prevention conventions, otherwise reviews become inconsistent and verification claims go unverified.
Core Features & Use Cases
- TRUST 5 Quality Gates: Defines the five mandatory gates (Tested, Readable, Unified, Secured, Trackable) with coverage targets of 85% package minimum and 90%+ for critical packages like internal/cli and internal/template.
- Go Test Isolation Rules: Codifies t.TempDir() usage, macOS path pitfalls, the ban on OTEL env vars in parallel tests, and full-suite re-run requirements after test fixes.
- Hardcoding Prevention & Agent Boundaries: Centralizes env var names in envkeys.go, thresholds in defaults.go, restricts AskUserQuestion to the orchestrator, and enforces the archived-agent rejection contract with 8 retained delegation targets.
- Use Case: A quality-specialist reviewing a new Go test file loads this skill to confirm the test uses t.TempDir(), avoids t.Setenv on HOME, and that any coverage claim cites the actual go test output observed in this run.
Quick Start
Load the moai-adk-go best practices reference and review my new Go test file for TRUST 5 compliance and test isolation violations.