link-workspace-packages

Link consumer packages to providers via workspace commands in monorepos.

Updated May 4, 2026
One-click install
npx skills add https://github.com/clarivex-tech/pervaxis-forge --skill link-workspace-packages-clarivex-tech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: link-workspace-packages
Source: https://github.com/clarivex-tech/pervaxis-forge/tree/main/pervaxis-forge-launchpad/.claude/skills/link-workspace-packages
Command: npx skills add https://github.com/clarivex-tech/pervaxis-forge --skill link-workspace-packages-clarivex-tech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Link consumer packages to providers via workspace commands to wire dependencies across a monorepo without manual edits or fragile tsconfig paths.

Core Features & Use Cases

  • Detect consumer and provider packages and wire dependencies using the workspace protocol across npm, pnpm, yarn, or bun.
  • Automatically resolve and symlink workspace packages to prevent "Cannot find module" errors.
  • Import providers by their workspace name from any package in the workspace.
  • Use case: After generating new packages, quickly connect them to existing apps so builds and tests run smoothly.

Quick Start

From the consumer project directory, run the workspace linking command appropriate for your package manager to connect the provider package.

Frequently Asked Questions about link-workspace-packages

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

FAQPage Schema
How do I link workspace packages across directories in a monorepo?

Workspace package linking resolves cross-package dependencies in monorepos by connecting consumer packages to providers via the workspace protocol. It uses npm, pnpm, yarn, or bun workspace commands to symlink packages across multiple directories instead of manual tsconfig edits.

Why do I get Cannot find module errors for workspace packages after splitting my monorepo?

Cannot find module errors occur when consumer packages lack proper workspace links to providers. Symlinking workspace packages through your package manager resolves these missing imports by enforcing the workspace protocol instead of relying on fragile manual path configurations.

Does this workspace linking approach work with pnpm, yarn, and bun monorepos?

Yes, workspace linking supports npm, pnpm, yarn, and bun monorepos. It detects provider imports and applies the correct workspace protocol for your package manager to validate that consumers specify dependencies via workspace links rather than manual edits.

What's the best way to wire new packages into existing monorepo apps without manual tsconfig paths?

The best way to wire new packages into monorepo apps without manual tsconfig paths is using workspace protocol linking. This automatically symlinks provider packages, allowing consumers to import providers by workspace name and ensuring builds and tests run smoothly.

When should I use workspace protocol links instead of manually editing package dependencies?

Use workspace protocol links instead of manual edits whenever packages are split across multiple directories in a monorepo. It validates correct workspace protocol usage, detects provider imports, and prevents fragile configuration issues associated with manual dependency path edits.