What is monorepo-management?

A workspace guide for keeping multiple software packages in one repository, called a monorepo. It covers workspace tools, package names, shared configuration, dependencies, testing, builds, and versioning.

Use it to create or audit a monorepo, add a workspace, organize shared TypeScript, JavaScript, or Go packages, and plan their builds, dependencies, and releases.

It helps avoid inconsistent package structures and duplicated setup across related projects. It also addresses how to run checks only for packages affected by a change.

monorepo-management — Skill for Claude Code and Codex by soulcodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add soulcodex/agentic --skill monorepo-management

Clone the repo

git clone --depth 1 https://github.com/soulcodex/agentic

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/soulcodex/agentic/monorepo-management.svg)](https://agentmods.dev/skills/soulcodex/agentic/monorepo-management)

Your own site

<a href="https://agentmods.dev/skills/soulcodex/agentic/monorepo-management"><img src="https://agentmods.dev/badge/skills/soulcodex/agentic/monorepo-management.svg" alt="Measured on agentmods" height="20"></a>

Per session 63 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,040 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00063	$0.01040
Opus 5	$0.00032	$0.00520
Sonnet 5	$0.00013	$0.00208
Haiku 4.5	$0.00006	$0.00104

Measured 3d ago against content hash 77b21f4bc491, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

monorepo-management scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/development/monorepo-management/SKILL.md · 153 lines

How it starts

The opening of the file, as written. The whole thing — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Monorepo Management Skill

Step 1 — Choose the Workspace Tool

Language	Tool	When to use
TypeScript/JS	pnpm workspaces	Default for JS/TS monorepos
TypeScript/JS	Turborepo	Add on top of pnpm when build caching matters
Go	Go workspaces (`go.work`)	Multiple Go modules in one repo
Mixed	Nx	When you need cross-language task orchestration

For most TypeScript projects: pnpm + Turborepo. For Go: go workspaces for local development, separate modules for independent versioning.

Step 2 — Package Naming

Follow a consistent naming scheme:

@acme/api          ← backend service
@acme/web          ← frontend application
@acme/ui           ← shared component library
@acme/core         ← shared domain types and utilities
@acme/config-ts    ← shared TypeScript config
@acme/config-rslint ← shared Rslint config

Rules:

Use a consistent org prefix (@acme/, @org/).
Separate packages for separate concerns — do not bundle the UI and the API.
Keep shared config packages (tsconfig, rslint, and any retained eslint config) in packages/config-*/.

Step 3 — Shared Tooling at Root

Place shared configuration at the repo root; packages extend it:

monorepo/
  package.json          ← workspace root — scripts + dev deps
  pnpm-workspace.yaml   ← workspace package globs
  turbo.json            ← Turborepo pipeline
  tsconfig.base.json    ← shared TS config
  rslint.config.ts      ← shared Rslint config
  .gitignore
  packages/
    api/
    web/
    ui/
    core/

# pnpm-workspace.yaml
packages:
  - "packages/*"
  - "apps/*"

Step 4 — Inter-Package Dependencies

Use workspace protocol for internal dependencies:

{
  "dependencies": {
    "@acme/core": "workspace:*"
  }
}

Rules:

Never use a published version of an internal package in development.
Dependency direction: apps/* → packages/*; packages/* must not depend on apps/*.
Circular dependencies between packages are forbidden.

Read the full file on GitHub · 153 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

3d ago Changed · +1 lines 77b21f4bc491
6d ago First seen · 152 lines · 63 tokens per session scan A 129e314b8403

Subscribe to this mod's changes

monorepo-management is a skill published in the GitHub repository soulcodex/agentic (10 stars, last pushed 2d ago), licensed MIT. It adds 63 tokens to every session and 1,040 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

DevOps and cloud Git and workflow Planning agentic ai ai-tools architecture build cli design-pattern monorepo workspace

repo-hygiene

Use when the scheduled repo-hygiene workflow runs from GitHub Actions (or an operator dry-run) to scan the repository for small, certain docs/test/code hygiene issues and fix them as one batched branch.

QwenLM/qwen-code · 48 tokens

create-issue

Draft and submit a GitHub issue from a user idea or bug description, with bilingual body and correct labels.

QwenLM/qwen-code · 26 tokens

docs-update-from-diff

Review local code changes with git diff and update the official docs under docs/ to match. Use when the user asks to document current uncommitted work, sync docs with local changes, update docs after a feature or refactor, or when phrases like "git diff", "local changes", "update docs", or "official docs" appear.

QwenLM/qwen-code · 75 tokens

monorepo-management