workspace-dependency-check

Diagnose pnpm workspace module resolution failures and suggest fixes.

6|Updated Mar 11, 2026

Search Tags:#fix #workspace #pnpm #monorepo #diagnosis #dependency #module-resolution

Ready to run

npx skills add https://github.com/open-hax/opencode-skills --skill workspace-dependency-check

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: workspace-dependency-check
Source: https://github.com/open-hax/opencode-skills/tree/main/.opencode/skills/workspace-dependency-check
Command: npx skills add https://github.com/open-hax/opencode-skills --skill workspace-dependency-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill helps identify why a package cannot be resolved in a pnpm workspace and guides you to fix the root cause.

Core Features & Use Cases

Inspect package.json to confirm the local package name and dependencies.
Validate workspace configuration in pnpm-workspace.yaml and ensure paths include the target package.
Verify main and exports fields point to existing files and align with consumer expectations.
Use cases include missing workspace paths, incorrect exports, and stale or missing dependencies in monorepos.

Quick Start

Run this skill when you encounter Module not found errors in a pnpm workspace to diagnose the cause and apply the correct fix.

Frequently Asked Questions about workspace-dependency-check

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

FAQPage Schema

Why does pnpm workspace module resolution fail in my monorepo?▼

pnpm workspace module resolution fails when local package names are mismatched, pnpm-workspace.yaml paths exclude the target package, or main and exports fields point to non-existent files. This skill diagnoses these specific configuration mismatches to identify the root cause.

How do I fix missing workspace dependencies in a pnpm monorepo?▼

To fix missing workspace dependencies in a pnpm monorepo, you must validate consumer package.json dependencies and ensure pnpm-workspace.yaml includes the target package path. This skill inspects these configurations and suggests concrete fixes for stale dependencies.

How do I validate package.json exports fields for local packages?▼

Validating package.json exports fields requires checking that main and exports paths point to existing files and align with consumer expectations. This skill verifies these fields against your local workspace setup to resolve misconfigured package imports.

What causes module not found errors in pnpm workspaces?▼

Module not found errors in pnpm workspaces are caused by incomplete workspace definitions, incorrect package.json names, or misaligned exports fields. This skill diagnoses these resolution failures by inspecting your workspace configuration and package metadata.

Does this workspace diagnosis support monorepos with complex package structures?▼

Yes, this workspace diagnosis supports monorepos with complex package structures by validating local package names, pnpm-workspace.yaml paths, main and exports fields, and consumer dependencies across the workspace to ensure proper module resolution.

What should I do when pnpm-workspace.yaml paths do not resolve local packages?▼

When pnpm-workspace.yaml paths do not resolve local packages, you must verify the paths include the target package and match the directory structure. This skill validates your workspace configuration and suggests corrections for incomplete definitions.