link-workspace-packages

Wire consumer package dependencies to providers using workspace syntax across pnpm, yarn, bun, or npm.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Wiring dependencies between packages in a monorepo can be fragile and error-prone when manual edits to package manifests are required. This Skill provides automated workspace-based linking to ensure consumers resolve providers consistently across managers like pnpm, yarn, npm, or bun.

Core Features & Use Cases

  • Detect Package Manager: automatically detect the active workspace manager and apply the correct linking syntax.
  • Cross-Manager Linking: wire dependencies between consumer and provider packages using workspace protocol across pnpm, yarn, npm, and bun.
  • Validation & Verification: verify node_modules symlinks and manifest correctness to prevent resolution errors; provide guidance for common troubleshooting scenarios.

Quick Start

Link a consumer package to its providers using the workspace syntax appropriate for your package manager.

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 across different package managers?

Linking workspace dependencies in a monorepo requires identifying consumer and provider packages, then applying the correct workspace protocol syntax for your active package manager like pnpm, yarn, npm, or bun.

What is the workspace protocol for linking local packages in pnpm or yarn?

The workspace protocol for linking local packages uses a specific syntax like workspace:* in your package manifest to symlink provider packages into consumer node_modules, ensuring consistent resolution across pnpm, yarn, bun, or npm.

Why do monorepo dependency links break after manually editing package manifests?

Monorepo dependency links break after manual manifest edits due to incorrect workspace syntax or hoisting behavior. Validating root manifests, workspace configuration, and node_modules symlinks prevents these resolution errors.

Does this workspace linking approach work with both bun and npm workspaces?

Yes, cross-manager linking works with bun and npm workspaces by automatically detecting the active manager, validating root manifests, and applying the correct workspace protocol syntax for each environment.

How to verify node_modules symlinks are correct after wiring monorepo packages?

To verify node_modules symlinks after wiring monorepo packages, check that consumer packages resolve to provider packages correctly, validate root manifests, and confirm hoisting behavior matches the active package manager configuration.

What's the best way to automate dependency linking in a monorepo instead of manual edits?

The best way to automate monorepo dependency linking is using a tool that detects the package manager, applies the correct workspace syntax across pnpm, yarn, bun, or npm, and verifies node_modules symlinks to prevent resolution errors.