PlugWiki

monorepo-management skill (wshobson): set up and speed up monorepos

Makes your agent set up and tune JavaScript monorepos with pnpm workspaces, Turborepo or Nx.

Installs
14.8K
on skills.sh
Stars
42.1K
on GitHub
Files
1
besides SKILL.md
Updated
Oct 2026
last repo commit

This skill gives your agent a playbook for monorepos. It recommends pnpm workspaces and Turborepo for most teams, shows Nx as the feature-rich option, and covers turbo.json setup, package layout, shared TypeScript and ESLint configs, caching, GitHub Actions, and versioning with Changesets.

It triggers when you set up a monorepo, optimize builds, or manage shared dependencies. It tells the agent to run scaffold commands such as npx create-turbo@latest, and its publishing steps can push packages to npm.

Good for

  • Teams moving from many repos to one monorepo
  • Developers fixing slow builds and cache misses in a monorepo
  • Maintainers publishing several packages with Changesets

Install monorepo-management

Claude Code

  1. 1

    Copy this prompt.

    Install the monorepo-management skill in Claude Code. Run this command:
    
    /plugin marketplace add wshobson/agents
    /plugin install developer-essentials@claude-code-workflows
    
    Then check that it loaded and tell me how to use it.
  2. 2

    Paste it into Claude Code. It shows the change and asks before running it.

Plugin route: the README shows the pattern with the python-development plugin; the plugin that holds this skill is developer-essentials, so the command swaps in that name from its manifest. It adds the repo's 11 skills for that plugin and 1 agent (monorepo-architect), and the repo has no hooks file or .mcp.json under that plugin. Single-skill route: the README says the skills installers add a skill without the plugin's agents, commands or hooks.

From the project README. Source.

What's in the skill

When it loads

Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.

Sections in SKILL.md

  1. When to Use This Skill
  2. Core Concepts
  3. 1. Why Monorepos?
  4. 2. Monorepo Tools
  5. Turborepo Setup
  6. Initial Setup
  7. Configuration
  8. Package Structure
  9. Detailed patterns and worked examples
  10. Best Practices
  11. Common Pitfalls
  12. Publishing Packages

Key facts

Installs on skills.sh
14,808 as of 2 Nov 2026
License
MIT
Last commit in the repo
2026-10-30

What it includes

  • Why monorepos, and which tools to choose

    Recommends pnpm workspaces, Turborepo for most teams, Nx when you need more features, and calls Lerna maintenance mode.

    Read · Core concepts

  • npx create-turbo@latest, turbo.json and root scripts

    Scaffolds a repo with apps and packages, sets task dependencies and cached outputs, and notes that Turborepo 2 uses tasks instead of pipeline (npx @turbo/codemod migrate upgrades a 1.x config).

    Try: “Set up a Turborepo monorepo with a Next.js app, a docs site and a shared ui package.”

    Runs code · Turborepo setup

  • Shared package.json exports and tsup builds

    A worked example of an @repo/ui package with exports, build and type-check scripts.

    Write · Package structure

  • Workspace config, filters, Nx generators, affected runs

    pnpm-workspace.yaml, .npmrc options, pnpm --filter commands, and Nx creation, project generation and affected-only tasks.

    Runs code · references/details.md: pnpm and Nx

  • TypeScript, ESLint, shared UI, utilities and types

    Patterns for shared base configs and three ways to share code between packages.

    Write · Shared configs and code sharing

  • Cache inputs and outputs; npx turbo login and link

    Tuning Turborepo caching, and a remote cache route through Vercel that signs you in and links the repo.

    Runs code · Build optimization and remote cache

  • GitHub Actions for build, test, lint, and deploy only what changed

    Workflow examples, including an Nx check that deploys only the app that changed.

    Write · CI/CD

  • pnpm changeset, version and publish, plus a release workflow

    Adds @changesets/cli, creates changesets, bumps versions and publishes. The example workflow uses GITHUB_TOKEN and NPM_TOKEN secrets.

    Runs code · Publishing with Changesets

  • Eight practices and six common pitfalls

    Includes avoiding circular dependencies and phantom dependencies, and setting cache inputs correctly.

    Read · Best practices and pitfalls

From the official docs

Permissions

Medium risk

The skill tells the agent to run scaffold commands through npx, edit repo config, and publish packages to npm. Work on a branch and approve publish steps yourself.

What it can do

  • Read your data
  • Create and change things
  • Delete things
  • Read-only mode

Watch out for

  • Publishing can push packages to npm

    The Changesets section ends with pnpm changeset publish, and the example workflow passes NPM_TOKEN. Run publish steps yourself and keep tokens in CI secrets. github.com

  • Scaffold commands download and run npm packages

    npx create-turbo@latest and npx create-nx-workspace@latest fetch and run the latest versions. Check the prompts before accepting. github.com

  • Remote caching signs you in and links the repo

    npx turbo login and npx turbo link connect the repo to the Vercel remote cache. Skip them if you do not want build artifacts stored there. github.com

  • The example clean script deletes node_modules

    The root package.json example has a clean script that ends in rm -rf node_modules. Check the script before running it. github.com

Technical details
Turning on read-onlyThe SKILL.md defines no read-only switch.
Talks tonpm registry, for scaffolding and publishing. Vercel remote cache, if you run npx turbo login and link
Scopes
  • Runs npx create-turbo@latest, create-nx-workspace, pnpm and turbo commands

  • Writes turbo.json, pnpm-workspace.yaml, package.json files and CI workflows

  • Publishing steps use pnpm changeset publish and an NPM_TOKEN secret

Questions

What does the monorepo-management skill do?

It makes your agent set up and tune monorepos with pnpm workspaces, Turborepo or Nx, including shared configs, caching, CI and package versioning.

How do I install it?

Use the install box on this page: it offers the developer-essentials plugin or this skill alone, and the skill folder is SKILL.md plus one reference file.

Turborepo or Nx?

The SKILL.md recommends Turborepo for most teams and calls Nx feature-rich but complex. It recommends pnpm workspaces as the package manager.

Will it publish my packages?

The SKILL.md's publishing section shows pnpm changeset publish and a release workflow that uses an NPM_TOKEN secret. Review the publish step before you approve it, or run it yourself.

Is it the same as the developer-essentials plugin?

No. The skill lives inside that plugin in the wshobson/agents repo. The plugin install adds the repo's 11 skills for it plus one agent; the skills-only command adds just this skill.

Is it safe to run?

It runs scaffold and package commands and can publish to npm if you let it. Work in a branch and review each command. The Watch out list has the details.

Information

updated Nov 2, 2026

Repository
wshobson/agents
Folder
plugins/developer-essentials/skills/monorepo-management

wshobson/agentsskills.sh

Sources

Docs, issue trackers and discussions this page is built from.

Show all 4
  1. wshobson/agents README · github.com
  2. developer-essentials plugin manifest · github.com
  3. monorepo-management SKILL.md · github.com
  4. details.md · github.com

Updated Nov 2, 2026.