Run type, lint, test, and build checks across all monorepo apps and packages.
npx skills add https://github.com/gunning4it/openorder --skill monorepo-check
Please help me install this Agent Skill. Skill: monorepo-check Source: https://github.com/gunning4it/openorder/tree/main/.claude/skills/monorepo-check Command: npx skills add https://github.com/gunning4it/openorder --skill monorepo-check
Coordinate and validate changes across a Turborepo monorepo by running a comprehensive set of checks to catch type, lint, test, and build issues before PRs.
Run the monorepo check workflow from the repository root to verify a clean state and cross-package integrity.
High-intent search queries and answers about installing and using this skill.
Run a comprehensive monorepo check from the repository root to validate type checking, linting, tests, and builds across all apps and packages. This pre-PR validation surfaces cross-package inconsistencies and provides actionable remediation steps for any detected failures.
The best way to catch cross-package build failures is running a full suite of monorepo checks across all apps and packages. This validates builds, surfaces inconsistencies from cross-package changes, and guides remediation for failures in apps/api, apps/storefront, apps/dashboard, apps/widget, and packages/*.
Yes, you can validate type, lint, and test failures simultaneously by applying a pre-PR validation workflow across all apps and packages. It enforces type checking, linting, testing, and build validation across apps/api, apps/storefront, apps/dashboard, apps/widget, and packages/*.
To fix type and build issues after cross-package changes, use the guided debugging output from the monorepo check workflow. It provides targeted steps for common failures across apps like api, storefront, dashboard, and widget to help remediate detected inconsistencies.
Yes, monorepo validation works for specific apps including storefront, dashboard, widget, and api. It runs type checking, linting, testing, and build validation across these apps and packages/* to ensure repository health before merging changes.
You need to run monorepo checks after modifying shared packages to detect cross-package type, lint, test, and build failures. Applying validation after cross-package changes ensures repository health by identifying inconsistencies across all dependent apps and packages.
pau-vegaAudit pnpm and Turborepo workspace packages for required scripts and config files.
cedricfarinazzoRebase a PR branch on main and push only when a merge commit is created.
oimiragieoAnalyze ASTs to detect naming, formatting, and structural inconsistencies in code.
robertzengcnAggregate code quality metrics from multiple tools into a weighted 0-10 composite score.
