link-workspace-packages

Enforce the pnpm workspace protocol to resolve internal package dependency issues.

26|4|Updated Jul 21, 2026
One-click install
npx skills add https://github.com/skyf0xx/hedgehog --skill link-workspace-packages-skyf0xx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: link-workspace-packages
Source: https://github.com/skyf0xx/hedgehog/tree/main/src/skills/link-workspace-packages
Command: npx skills add https://github.com/skyf0xx/hedgehog --skill link-workspace-packages-skyf0xx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves common monorepo dependency issues where packages fail to import sibling modules, preventing build errors like TS2307 or module resolution failures.

Core Features & Use Cases

  • Workspace Linking: Correctly wires up internal package dependencies using the pnpm workspace protocol.
  • Dependency Debugging: Provides a structured approach to verify and fix broken symlinks in a monorepo environment.
  • Use Case: When you add a new UI component library to your monorepo and your main application fails to import it, this skill ensures the package is correctly linked as a workspace dependency.

Quick Start

Use the link-workspace-packages skill to add the local ui package as a dependency to the current application 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 fix TypeScript module resolution errors in a pnpm monorepo?

Fix TypeScript module resolution errors in a pnpm monorepo by enforcing the workspace protocol to correctly wire internal package dependencies. This ensures proper symlinks and strict isolation between sibling packages, resolving broken module imports.

Why does my monorepo application fail to import a sibling UI package?

Monorepo applications fail to import sibling packages due to missing symlinks and incorrect dependency declarations. Enforcing the pnpm workspace protocol correctly links the local package as a workspace dependency, ensuring strict isolation and resolving build errors like TS2307.

What's the best way to debug broken symlinks in a pnpm workspace?

The best way to debug broken symlinks in a pnpm workspace is using a structured approach to verify internal package dependencies. Enforcing the workspace protocol ensures proper dependency declaration and fixes broken module imports between sibling packages.

Does this approach work for resolving TS2307 errors when adding new packages to a monorepo?

Yes, resolving TS2307 errors when adding new packages to a monorepo works by enforcing the pnpm workspace protocol. This correctly links the new package as a workspace dependency, ensuring proper module resolution and preventing build failures.

How do I enforce strict isolation for internal package dependencies in a pnpm monorepo?

Enforce strict isolation for internal package dependencies in a pnpm monorepo by applying the workspace protocol. This ensures proper dependency declaration between sibling packages, maintaining strict isolation and preventing broken symlinks and module resolution failures.