link-workspace-packages

Detect the package manager and link workspace packages across a monorepo.

Updated Dec 20, 2025
One-click install
npx skills add https://github.com/iqbal125/typescript_projects --skill link-workspace-packages-iqbal125
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: link-workspace-packages
Source: https://github.com/iqbal125/typescript_projects/tree/main/nestjs-react-monorepo-nx/.agents/skills/link-workspace-packages
Command: npx skills add https://github.com/iqbal125/typescript_projects --skill link-workspace-packages-iqbal125

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Monorepos often struggle with wiring new or existing packages across different package managers; this Skill simplifies linking workspace packages so dependencies are resolved consistently without manual tsconfig or package.json edits.

Core Features & Use Cases

  • Detects the active package manager (pnpm, yarn, bun, npm) and applies the correct workspace linking commands
  • Identifies consumer and provider packages and wires dependencies between them
  • Verifies symlinks in consumer/node_modules and ensures workspace resolution across tools

Quick Start

Run the appropriate workspace linking command for your package manager to connect a consumer package with its provider in the 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 packages in a monorepo?

To link workspace packages in a monorepo, you identify consumer and provider packages, declare dependencies in the consumer's package.json, and run the detected package manager's workspace linking commands to wire them together.

Why does my monorepo throw package resolution errors for sibling packages?

Package resolution errors for sibling packages occur when dependencies are not declared in the consumer's package.json or symlinks in node_modules are missing. Proper workspace linking resolves these issues by wiring the provider packages correctly.

Does this monorepo linking approach work with pnpm and yarn?

Yes, this workspace linking approach works with pnpm and yarn, as well as bun and npm. It detects the active package manager and applies the correct workspace commands to ensure proper dependency resolution.

What is the best way to wire dependencies after creating new packages in a monorepo?

The best way to wire dependencies for new monorepo packages is to detect the active package manager, identify the consumer and provider packages, and apply the appropriate workspace linking commands to verify symlinks in node_modules.

When do I need to wire dependencies across a monorepo?

You need to wire dependencies across a monorepo when new packages are created, imports from sibling packages exist, or resolution errors occur for workspace packages that require proper linking to be resolved.