pnpm-workspace
pnpm workspace monorepo management with filtering, catalogs, and shared configs. Use when setting up monorepos, managing workspace dependencies, filtering package commands, or sharing configuration across packages.
- Installs
- 184
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/oakoss/agent-skills --skill pnpm-workspace- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads pnpm-workspace automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
pnpm Workspace
Overview
pnpm workspaces provide built-in monorepo support through pnpm-workspace.yaml, the workspace: protocol for local package linking, and powerful filtering to run commands across specific packages. Catalogs enforce consistent dependency versions across all workspace packages.
When to use: Multi-package repositories, shared libraries with consuming apps, consistent dependency management across packages, running commands on subsets of packages.
When NOT to use: Single-package projects, projects already using npm/yarn workspaces (migration required), projects that need floating dependency versions per package.
Quick Reference
| Pattern | API / Config | Key Points |
|---|---|---|
| Define workspace | pnpm-workspace.yaml with packages globs | Globs match directories containing package.json |
| Link local package | "dep": "workspace:*" | Always resolves to local workspace package |
| Link with version range | "dep": "workspace:^1.0.0" | Fails install if local version does not satisfy range |
| Default catalog | catalog: key in pnpm-workspace.yaml | Single source of truth for dependency versions |
| Named catalog | catalogs: key with named groups | Multiple version sets (e.g., react18, react17) |
| Use catalog in package | "dep": "catalog:" or "dep": "catalog:name" | Resolved to actual version on pnpm publish |
| Filter by name | --filter <name> or -F <name> | Exact name or glob pattern (@scope/*) |
| Filter with dependencies | --filter "foo..." | Package and all its dependencies |
| Filter with dependents | --filter "...foo" | Package and all packages that depend on it |
| Filter by directory | --filter "./packages/app" | All packages under a directory path |
| Filter by git changes | --filter "[origin/main]" | Packages changed since a commit or branch |
| Exclude from filter | --filter "!foo" | Remove matching packages from selection |
| Run script in package | pnpm --filter <pkg> <script> | Runs script only in matched packages |
| Recursive run | pnpm -r run <script> | Runs script in all workspace packages |
| Install all | pnpm install | Single lockfile for entire workspace |
| Publish workspace pkg | pnpm publish | Replaces workspace: and catalog: with real versions |
| Inject workspace deps | inject-workspace-packages=true in .npmrc | Hard-links instead of symlinks; required for deploy |
| Script security (v10+) | allowBuilds in package.json | Lifecycle scripts blocked by default; opt-in per dep |
Common Mistakes
| Mistake | Correct Pattern |
|---|---|
Using workspace:* then publishing as-is | pnpm automatically replaces workspace:* with real versions on publish |
Forgetting to list directory in packages: | Every package directory must match a glob in pnpm-workspace.yaml |
Using npm install in workspace packages | Always use pnpm install from the workspace root |
| Hardcoding versions duplicated across packages | Use catalog: to centralize version definitions |
Running pnpm install inside a sub-package | Run from workspace root; use --filter to target packages |
Expecting --filter to match directory names | --filter matches package.json name field, not directory names |
Not escaping ! in zsh for exclude filters | Use \! or quote the filter: --filter="!foo" |
Using workspace: for non-workspace deps | workspace: protocol only works for packages defined in the workspace |
| Lifecycle scripts failing after pnpm 10 upgrade | pnpm 10 blocks scripts by default; add deps to allowBuilds in config |
Using pnpm deploy without inject-workspace-packages | Set inject-workspace-packages=true in .npmrc (required in pnpm 10) |
Delegation
- Workspace scaffolding: Use
Exploreagent to discover existing package structure - Dependency auditing: Use
Taskagent to check version consistency across packages
If the
turboreposkill is available, delegate build orchestration, task caching, and CI optimization to it. If thechangesetsskill is available, delegate versioning, changelog generation, and npm publishing to it.
References
- Workspace setup, workspace protocol, and catalogs
- Filtering packages for targeted commands
- Shared configuration across workspace packages
- Monorepo integration: pnpm + Turborepo + Changesets pipeline
FAQ
What does the pnpm-workspace skill do?
pnpm workspace monorepo management with filtering, catalogs, and shared configs. Use when setting up monorepos, managing workspace dependencies, filtering package commands, or sharing configuration across packages.
How do I install pnpm-workspace?
Run npx skills add https://github.com/oakoss/agent-skills --skill pnpm-workspace in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/pnpm-workspace/ (personal) or .claude/skills/pnpm-workspace/ (project).
Which AI agents can use pnpm-workspace?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is pnpm-workspace safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains pnpm-workspace?
It is published by oakoss in oakoss/agent-skills. It has 184 recorded installs.
More from oakoss/agent-skills
ui-ux-polish
oakoss/agent-skills
Iterative UI/UX polishing workflow for web applications. Use when improving visual polish, refining desktop and mobile UX separately, running iterative enhancement cycles, applying design patterns like glassmorphism or bento grids, or auditing accessibility and WCAG compliance. Use for Stripe-level visual quality, responsive optimization, and design system alignment.
playwright
oakoss/agent-skills
Open the skill to read its SKILL.md instructions.
coolify
oakoss/agent-skills
Coolify self-hosted PaaS for deploying applications, databases, and services via REST API and Git integration. Covers API authentication, deployment triggers, build packs (Nixpacks, Dockerfile, Compose), CI/CD with GitHub Actions webhooks, environment management, and Traefik proxy configuration. Use when deploying apps to Coolify, triggering deployments via API, configuring build packs, setting up GitHub Actions CI/CD pipelines, managing environment variables, or troubleshooting deployment failures.
application-security
oakoss/agent-skills
Open the skill to read its SKILL.md instructions.
find-skills
oakoss/agent-skills
Open the skill to read its SKILL.md instructions.
drizzle-orm
oakoss/agent-skills
Open the skill to read its SKILL.md instructions.
Popular ai & agents skills
google-agents-cli-publish
google/agents-cli
This skill should be used when the user wants to "publish an agent", "publish my ADK agent", "register an agent with Gemini", "publish to Gemini" (formerly Gemini Enterprise), or needs guidance on the agents-cli publish gemini command. Also use when the user wants to "manage agents in Agent Registry", "list/update/delete registered agents", or "register an MCP server". Covers ADK vs A2A registration modes, programmatic and interactive usage, flag reference, auto-detection from deployment metadata, Agent Registry fleet management, and troubleshooting. Part of the agents-cli skills suite. Do NOT use for deployment (use google-agents-cli-deploy).
google-agents-cli-eval
google/agents-cli
This skill should be used when the user wants to "run an evaluation", "evaluate my agent", "evaluate my ADK agent", "write an eval dataset", "analyze eval failures", "compare eval results", "optimize agent", or needs guidance on the Gemini platform eval methodology and the Quality Flywheel. Covers eval metrics, dataset schema, LLM-as-judge scoring, and common failure causes. Applies to any agents-cli project, whatever framework the agent is written in. Do NOT use for agent API code patterns (ADK: use google-agents-cli-adk-code), deployment (use google-agents-cli-deploy), or project scaffolding (use google-agents-cli-scaffold).
skill-creator
anthropics/skills
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
codex-pet
prime-skills/runcomfy-agent-skills
Codex Pet generator on RunComfy. Build a Codex-compatible Codex Pet spritesheet.webp + pet.json from a single reference image, drop it into ${CODEXHOME:-$HOME/.codex}/pets/ / and Codex picks it up as a custom Codex Pet next to the 8 built-ins. This skill produces the exact Codex Pet atlas Codex expects (1536x1872 PNG/WebP, 8 cols x 9 rows, 192x208 cells, 9 animation states — idle, running-right, running-left, waving, jumping, failed, waiting, running, review). Calls OpenAI GPT Image 2 edit ONCE via the local RunComfy CLI as runcomfy run openai/gpt-image-2/edit to produce a canonical Codex Pet pose, then assembles all 9 animation rows programmatically with ImageMagick micro-transforms — no Codex Pro, no $imagegen, no OPENAIAPIKEY required, only RUNCOMFYTOKEN. Triggers on "codex pet", "create codex pet", "make codex pet", "hatch codex pet", "/hatch image", "desktop pet codex", "codex pets", "spritesheet.webp", or any explicit ask to build a custom pet for OpenAI Codex.
full-output-enforcement
leonxlnx/taste-skill
Overrides default LLM truncation behavior. Enforces complete code generation, bans placeholder patterns, and handles token-limit splits cleanly. Apply to any task requiring exhaustive, unabridged output.
executing-plans
obra/superpowers
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available