link-workspace-packages

Link sibling workspace packages in npm, yarn, pnpm, or bun monorepos.

Updated May 5, 2026
One-click install
npx skills add https://github.com/Movchanets/Microservices_Learning --skill link-workspace-packages-movchanets
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: link-workspace-packages
Source: https://github.com/Movchanets/Microservices_Learning/tree/main/.agents/skills/link-workspace-packages
Command: npx skills add https://github.com/Movchanets/Microservices_Learning --skill link-workspace-packages-movchanets

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill fixes broken imports between sibling packages in a monorepo by adding the right workspace dependency instead of relying on path aliases or manual package edits.

Core Features & Use Cases

  • Workspace Linking: Adds package relationships using the correct syntax for pnpm, yarn, npm, or bun.
  • Resolution Troubleshooting: Helps when imports fail with missing module, failed to resolve import, or TypeScript resolution errors.
  • Monorepo Dependency Wiring: Supports the common workflow of connecting a newly created package to the package that consumes it.
  • Use Case: A frontend app imports a shared UI package from the same repo, and this Skill links them so the app can resolve the package through the workspace manager.

Quick Start

Use the link-workspace-packages skill to identify the consumer and provider packages in my monorepo and add the correct workspace dependency so imports resolve cleanly.

Frequently Asked Questions about link-workspace-packages

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

FAQPage Schema
How do I fix broken imports between sibling packages in a monorepo?

To fix broken monorepo imports, add the correct workspace dependency relationship between sibling packages instead of using manual path aliases. This wires the consumer package to receive the expected local link through your package manager.

How do I link a new local package to a consumer app in a pnpm or yarn workspace?

To link a local package in a pnpm or yarn workspace, use package-manager-specific workspace commands to add the provider package as a dependency, ensuring the consumer app resolves imports through the local workspace link.

Does this approach work for linking packages across npm, yarn, pnpm, and bun projects?

Yes, this workspace linking approach applies to npm, yarn, pnpm, and bun projects. It uses the correct syntax for each specific package manager to wire dependencies and verify that the consumer receives the local link.

Why does my monorepo fail to resolve imports for a newly created shared package?

Monorepo imports fail to resolve when a newly created shared package is not wired into the workspace configuration. You must add the correct workspace dependency relationship so the package manager links the sibling packages cleanly.

What is the best way to wire dependencies in a monorepo without manual package edits?

The best way to wire monorepo dependencies without manual edits is using built-in workspace linking commands. This adds the correct dependency relationship between sibling packages, avoiding broken imports and TypeScript resolution errors.