link-workspace-packages

Wire workspace package dependencies across npm, yarn, pnpm, and bun monorepos.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Wiring and linking workspace packages in a monorepo to ensure correct inter-package dependencies across npm, yarn, pnpm, and bun, preventing manual edits to tsconfig paths or package.json.

Core Features & Use Cases

  • Detect the active workspace manager (root package.json's packageManager field or lockfiles) to determine the correct workflow.
  • Wire dependencies between consumer and provider packages using the package manager's workspace commands.
  • Verify symlinks in consumer's node_modules and ensure consistent resolution across the workspace.

Quick Start

From a consumer package directory, add the provider as a workspace dependency using the appropriate command for your package manager and verify the linkage.

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

To link workspace packages, the process detects the root workspace configuration and applies the respective package manager's workspace commands to add dependencies. It validates node_modules symlinks to ensure correct inter-package resolution across the monorepo.

Why does my workspace package resolution fail when importing a sibling package?

Workspace package resolution errors occur when inter-package dependencies are not properly wired or symlinks in the consumer's node_modules are missing. You need to detect the active workspace manager and apply the correct workspace commands to link the provider package.

Can I use this to wire dependencies across different package managers like npm, yarn, pnpm, and bun?

Yes, it supports wiring dependencies across npm, yarn, pnpm, and bun. It detects the active workspace manager by checking the root package.json's packageManager field or lockfiles, then applies the appropriate workflow for that specific package manager.

What is the best way to add a new package as a workspace dependency without manual package.json edits?

The best way to add a new workspace dependency without manual package.json edits is to run the package manager's workspace commands from the consumer package directory. This automatically wires the provider package and verifies the symlinks for consistent resolution.

How does workspace package detection work for different package managers in a monorepo?

Workspace package detection works by identifying the active workspace manager through the root package.json's packageManager field or the presence of specific lockfiles. It uses this detection to determine the correct workflow for wiring dependencies across the monorepo.