link-workspace-packages

Wire inter-package dependencies in monorepos using the workspace protocol across pnpm, yarn, npm, and bun.

Updated Feb 12, 2026
One-click install
npx skills add https://github.com/Clogogo/audit_app --skill link-workspace-packages-clogogo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: link-workspace-packages
Source: https://github.com/Clogogo/audit_app/tree/main/.github/skills/link-workspace-packages
Command: npx skills add https://github.com/Clogogo/audit_app --skill link-workspace-packages-clogogo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Link workspace packages in monorepos to ensure consumer packages correctly resolve imports from sibling providers, avoiding manual edits to tsconfig paths or package.json dependencies.

Core Features & Use Cases

  • Detect the root workspace using packageManager or lockfiles and apply the correct linking command per manager.
  • Wire dependencies between consumer and provider packages, creating accurate symlinks in node_modules across npm, yarn, pnpm, and bun.
  • Use in scenarios like newly created packages needing wiring, fixing missing workspace imports, or resolving resolution errors for workspace packages.

Quick Start

Run a workspace-link operation to connect a consumer package to a provider package in your monorepo.

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 dependencies in a monorepo?

Link workspace dependencies in a monorepo by identifying the root package manager and applying the correct workspace protocol linking commands. This wires consumer packages to sibling providers and verifies symlinks in the consumer node_modules directory.

Why are my monorepo workspace imports failing to resolve?

Workspace imports fail when dependencies between consumer and provider packages are not properly wired. Resolve resolution errors by applying the correct linking commands for your specific package manager to create accurate symlinks in node_modules.

How do I wire a newly created package into an existing npm or pnpm workspace?

Wire a newly created package by running a workspace-link operation to connect the new consumer package to a provider package. This detects the root workspace via lockfiles or packageManager field and applies the proper linking command for npm or pnpm.

Does this monorepo linking approach work with yarn and bun workspaces?

Yes, workspace linking works with yarn and bun. It detects the root workspace environment and validates, then applies the correct linking commands across npm, yarn, pnpm, and bun to verify symlinks in consumer node_modules.

What is the best way to avoid manual tsconfig path edits when importing sibling packages?

To avoid manual tsconfig path edits, use the workspace protocol to wire dependencies between consumer and provider packages automatically. This ensures consumer packages correctly resolve imports from sibling providers without manual configuration.

When do I need to use the workspace protocol for package linking?

Use the workspace protocol for package linking when new packages are created, when a consumer imports a sibling package, or when resolution errors occur. It ensures consumer packages correctly resolve imports from sibling providers across monorepos.