scan-monorepo-health

You can detect dependency drift by auditing pnpm-workspace.yaml and root package.json to surface version mismatches across shared packages. This skill scans your Turborepo workspace configuration to identify dependency inconsistencies and generate remediation templates.

Monorepo health drift occurs when multiple packages in a workspace use conflicting dependency versions or misconfigured settings. Identifying this drift through configuration audits ensures long-term maintainability and prevents unexpected build failures across your Turborepo packages.

Yes, you can automatically audit turbo.json and pnpm-workspace.yaml to find version mismatches and configuration gaps. The scan produces structured findings that highlight catalog drift and workspace inconsistencies across your monorepo.

The best way to resolve dependency inconsistencies is to use generated remediation templates that guide developers in aligning versions. Scanning pnpm-workspace.yaml and turbo.json provides structured findings to fix configuration gaps and maintain workspace consistency.

Yes, the workspace health scan works without manual checks by automatically auditing your root package.json, turbo.json, and pnpm-workspace.yaml. It surfaces version mismatches and configuration gaps independently, providing structured findings for proactive maintenance.