link-workspace-packages

Add sibling packages as dependencies in monorepos using native package manager commands.

8|1|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/AIluffy/io --skill link-workspace-packages-ailuffy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: link-workspace-packages
Source: https://github.com/AIluffy/io/tree/main/.github/skills/link-workspace-packages
Command: npx skills add https://github.com/AIluffy/io --skill link-workspace-packages-ailuffy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of establishing dependencies between packages within a monorepo, ensuring they are correctly linked and resolvable by package managers.

Core Features & Use Cases

  • Cross-Package Dependency Management: Adds sibling packages as dependencies in package.json.
  • Package Manager Compatibility: Supports npm, yarn, pnpm, and bun with their respective workspace syntaxes.
  • Use Case: When you create a new UI component package and need to use it in your application package, this skill will automatically add the UI package as a dependency to the application package and ensure it's correctly linked.

Quick Start

Use the link-workspace-packages skill to add the '@org/ui' package as a dependency to the '@org/app' package using pnpm.

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 monorepo packages as dependencies in package.json?

To link monorepo packages, you add sibling packages as dependencies in package.json using native workspace protocols. This ensures correct symlink creation and module resolution across your monorepo packages.

Does this monorepo linking approach work with pnpm and bun?

Yes, this monorepo linking approach works with pnpm and bun, as well as npm and yarn. It uses each package manager's specific workspace syntax to ensure accurate dependency declaration and symlink creation.

Why does module resolution fail when adding a sibling package to my monorepo app?

Module resolution fails when you do not use the correct package manager-specific workspace protocols for dependency declaration. Proper linking requires adherence to these native commands to create accurate symlinks and resolve sibling packages.

What's the best way to manage inter-package dependencies in a monorepo?

The best way to manage inter-package dependencies is using native package manager workspace commands. This automatically establishes dependencies between packages, ensuring they are correctly linked and resolvable without manual symlink errors.

How do I add a new UI component package as a dependency to my monorepo application?

You add a new UI component package by declaring it as a dependency in your application's package.json using the correct workspace protocol. This automatically links the sibling package and makes it resolvable by your package manager.

Do I need to manually create symlinks when linking workspace packages?

No, you do not need to manually create symlinks. By using native package manager workspace protocols to declare dependencies, the package manager automatically handles symlink creation for accurate module resolution.