← ClaudeAtlas

mycomonorepo-quality-engineering-build-lifecyclelisted

Quality engineering procedures for Myco's npm workspace: build orchestration (make vs npm), cross-platform artifact validation, workspace dependency management, release workflow hardening, and CI/CD pipeline robustness. Use when setting up quality gates, debugging build failures, hardening release workflows, or managing workspace dependencies.
goondocks-co/myco · ★ 13 · AI & Automation · score 79
Install: claude install-skill goondocks-co/myco
# Monorepo Quality Engineering & Build Lifecycle Quality engineering procedures for establishing and maintaining robust build validation, dependency management, and CI/CD workflows in Myco's multi-package npm workspace. These procedures ensure silent failures are caught, cross-platform compatibility is validated, and release workflows are hardened against common failure modes. ## Prerequisites - Myco project with established npm workspace structure - Understanding of the multi-package architecture (packages/, ui workspaces) - Knowledge of npm workspace commands and lockfile management - Access to CI/CD configuration files - For Grove deployment: understanding of multi-tenant architecture and project isolation ## Procedure 1: Multi-stage Quality Gates Establish and maintain the distinction between fast development builds (`make build`) versus comprehensive CI validation (`make build-all`). ### Build Orchestration Strategy **Default Development Build** uses fast profile excluding integration tests: ```bash # Fast development build (default) make build # Executes: MYCO_TEST_PROFILE=fast make check, then npm run build # Excludes: tests/integration/, tests/smoke/, tests/daemon/integration/ ``` **Full CI Build** includes all test buckets: ```bash # Full CI validation pipeline make build-all # Executes: full test suite including integration tests, then npm run build ``` **Bundler-only Build** (skips all validation): ```bash # Bundler only - skips type checking and tests npm