package-manager

Name: package-manager
Availability: InStock
Author: estebandrg

Enforce dependency placement and workspace boundaries in Liftera's pnpm monorepo.

Updated Jan 15, 2026

Search Tags:#dependencies #workspace #pnpm #monorepo #package.json #lockfile #pnpm-workspace.yaml

Ready to run

npx skills add https://github.com/estebandrg/liftera --skill package-manager

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: package-manager
Source: https://github.com/estebandrg/liftera/tree/main/skills/package-manager
Command: npx skills add https://github.com/estebandrg/liftera --skill package-manager

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Liftera's monorepo often drifts in dependency management, causing inconsistent installs and broken builds. This Skill defines and enforces workspace boundaries and scoped dependencies to keep the monorepo healthy and predictable.

Core Features & Use Cases

Enforces workspace boundaries defined by pnpm-workspace.yaml to prevent cross-project drift.
Ensures dependencies are added to the narrowest applicable scope (apps//package.json, packages//package.json, or root package.json).
Maintains lockfile consistency by requiring pnpm-lock.yaml updates on dependency changes.
Use Case: When onboarding a new package or updating a shared dependency, apply these rules to keep the monorepo stable.

Quick Start

Update a dependency in the correct scope, then run pnpm install and commit pnpm-lock.yaml.

Frequently Asked Questions about package-manager

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I enforce pnpm workspace boundaries in a monorepo?▼

Enforcing pnpm workspace boundaries requires validating dependency placement against pnpm-workspace.yaml to prevent cross-project drift and ensure packages are scoped correctly within the monorepo.

Where should dependencies be added in a pnpm monorepo?▼

Dependencies should be added to the narrowest applicable scope, such as apps/*/package.json or packages/*/package.json, with root tooling placed in the root package.json to maintain monorepo stability.

Why does updating package.json break my pnpm monorepo builds?▼

Builds break when pnpm-lock.yaml is not updated alongside package.json. Running pnpm install after dependency changes ensures lockfile consistency and prevents broken monorepo installs.

Does this dependency management approach require pnpm?▼

Yes, this dependency management approach requires pnpm. It relies on pnpm-workspace.yaml for workspace boundaries and pnpm-lock.yaml for lockfile consistency to keep monorepo installs predictable.

What is the best way to onboard a new package in a pnpm workspace?▼

The best way to onboard a new package is to add it within the pnpm-workspace.yaml boundaries, scope its dependencies in the correct package.json, run pnpm install, and commit the updated pnpm-lock.yaml.