scan-monorepo-health

Detect dependency drift and workspace inconsistencies in Turborepo monorepos.

Updated Aug 23, 2026

Search Tags:#automation #linting #workspace #pnpm #monorepo #turbo #dependency-drift

Ready to run

npx skills add https://github.com/TrevorPLam/agency --skill scan-monorepo-health

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: scan-monorepo-health
Source: https://github.com/TrevorPLam/agency/tree/main/.windsurf/skills/scan-monorepo-health
Command: npx skills add https://github.com/TrevorPLam/agency --skill scan-monorepo-health

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps engineering teams identify dependency drift and configuration mismatches in a Turborepo-style workspace, enabling proactive maintenance and consistency.

Core Features & Use Cases

Audit workspace configurations: pnpm-workspace.yaml, turbo.json, and root package.json to surface version mismatches.
Detect catalog drift and misconfigurations across packages and apps within the monorepo.
Generate actionable remediation templates for resolving issues and maintaining consistency across the workspace.

Quick Start

Run the monorepo health scan to detect dependency drift and misconfigurations across the workspace.

Frequently Asked Questions about scan-monorepo-health

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

FAQPage Schema

How do I detect dependency drift in a pnpm monorepo?▼

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.

What is monorepo health drift and how does it affect workspace consistency?▼

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.

Can I audit turbo.json and pnpm-workspace.yaml for version mismatches automatically?▼

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.

What's the best way to resolve dependency inconsistencies across Turborepo packages?▼

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.

Does this workspace health scan work without manual package version checks?▼

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.