link-workspace-packages

Automates dependency wiring for local workspace packages in JavaScript/TypeScript monorepos across npm, yarn, pnpm, and bun.

3|1|Updated Apr 18, 2026
One-click install
npx skills add https://github.com/wahidyankf/ose-primer --skill link-workspace-packages-wahidyankf
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: link-workspace-packages
Source: https://github.com/wahidyankf/ose-primer/tree/main/.opencode/skills/link-workspace-packages
Command: npx skills add https://github.com/wahidyankf/ose-primer --skill link-workspace-packages-wahidyankf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates frustrating resolution errors for local workspace packages in JavaScript/TypeScript monorepos, removing the need for manual tsconfig path hacks or error-prone manual package.json edits that can break dependency resolution.

Core Features & Use Cases

  • Multi-package manager support: Natively handles workspace linking syntax for npm, yarn, pnpm, and bun.
  • Automated dependency wiring: Correctly declares dependencies between sibling workspace packages to fix "cannot find module", TS2307, and similar import errors.
  • Use Case: If you just generated a new shared UI library in your monorepo and your consumer app cannot import it, this Skill handles the correct dependency declaration and symlink setup for your project's package manager.

Quick Start

Use the link-workspace-packages skill to wire up the new @org/utils package as a dependency for your @org/dashboard app to resolve the import error.

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 cannot find module errors for local packages in a monorepo?

Fix cannot find module errors by correctly declaring dependencies between sibling workspace packages. This ensures proper symlink creation and module resolution without requiring manual tsconfig path patches or package.json edits.

Does this approach support workspace linking for pnpm and bun monorepos?

Yes, workspace linking natively handles syntax for npm, yarn, pnpm, and bun monorepos. It automates correct dependency declaration across these package managers to resolve local package imports.

What is the best way to link a newly generated shared library to a consumer app?

The best way to link a shared library is using native package manager workspace commands. This correctly wires the dependency and sets up symlinks for your project's specific package manager.

Why does @org/* module resolution fail when I add sibling package imports?

@org/* module resolution fails when dependencies between sibling workspace packages are not declared correctly. Automating this declaration fixes TS2307 and similar import resolution errors.

How to resolve TS2307 import errors in a JavaScript monorepo without tsconfig hacks?

Resolve TS2307 errors by automating correct dependency declaration between workspace packages. This native package manager approach eliminates the need for manual tsconfig path hacks or ad-hoc package.json edits.

Do I need to manually edit package.json to fix broken workspace symlinks?

No, you do not need to manually edit package.json to fix broken workspace symlinks. Automating dependency declaration using native workspace commands ensures correct symlink creation and dependency resolution.