link-workspace-packages

Detect the package manager and wire workspace dependencies across monorepo packages.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/veraclins-dev/dev --skill link-workspace-packages-veraclins-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: link-workspace-packages
Source: https://github.com/veraclins-dev/dev/tree/main/.cursor/skills/link-workspace-packages
Command: npx skills add https://github.com/veraclins-dev/dev --skill link-workspace-packages-veraclins-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Link workspace packages in a monorepo to resolve dependencies across different package managers without manual edits.

Core Features & Use Cases

  • Detects the project’s active package manager and chooses the correct workspace syntax
  • Adds provider dependencies in consumer projects using workspace protocols (pnpm, yarn, npm, bun)
  • Verifies symlinks in consumer/node_modules to ensure proper resolution and avoid phantom dependencies

Quick Start

Run a workspace-aware command in the consumer project to link 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 in a monorepo without manual edits?

To link workspace packages in a monorepo, you can use workspace commands to wire dependencies between consumer and provider packages. This automatically applies the correct workspace syntax and verifies symlinks in consumer node_modules.

Does this approach work with pnpm, yarn, npm, and bun workspaces?

Yes, workspace package linking works across pnpm, yarn, npm, and bun. The process detects the project's active package manager and applies the correct workspace protocol syntax for that specific tool.

How do I resolve imports from a sibling package in a monorepo?

You resolve imports from a sibling package by adding the provider package as a dependency in the consumer project. The workspace tooling then connects them and ensures symlinks are properly created for module resolution.

Why do I have phantom dependencies in my monorepo node_modules?

Phantom dependencies in monorepo node_modules happen when symlinks are not properly verified or workspace protocols are not applied. Linking workspace packages correctly verifies symlinks in consumer node_modules to avoid this issue.

What is the best way to add a new package to an existing monorepo?

The best way to add a new package to a monorepo is by using workspace-aware commands in the consumer project. This links the new provider package using the appropriate workspace protocol without requiring manual package.json edits.

When do I need to use workspace protocols for monorepo dependencies?

You need to use workspace protocols for monorepo dependencies when wiring consumer and provider packages together. This ensures proper linkage across different package managers and verifies symlinks to prevent module resolution failures.