vscode-monorepo-forge

Generates VS Code workspace, debug, task, and Turborepo pipeline configurations for monorepos.

1|Updated Aug 25, 2026
One-click install
npx skills add https://github.com/sabiscore/swarmxq --skill vscode-monorepo-forge-sabiscore
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vscode-monorepo-forge
Source: https://github.com/sabiscore/swarmxq/tree/main/.ai/skills/vscode-monorepo-forge
Command: npx skills add https://github.com/sabiscore/swarmxq --skill vscode-monorepo-forge-sabiscore

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting up VS Code for a monorepo involves tedious, error-prone configuration across many files: multi-root workspace definitions, per-package settings, cross-package debug configs, and task runners. This Skill generates complete, copyable configuration files so developers stop fighting Explorer noise, broken ESLint resolution, and single-package debugging. ## Core Features & Use Cases - Multi-root workspace generation: Produces a .code-workspace file with folder mappings, file/watcher/search exclusions, workspace TypeScript version pinning, and recommended extensions. - Cross-package debugging: Generates launch.json with per-app debug configurations (Next.js, Fastify, Jest, Prisma) plus compound configs to debug web and API simultaneously. - Task and pipeline automation: Creates tasks.json for turbo dev/build/typecheck and Prisma commands, plus a turbo.json pipeline with caching and dependency rules. - Use Case: A developer joins a pnpm + Turborepo project with a Next.js frontend and Fastify API. They ask to set up VS Code, and receive a complete .code-workspace, launch.json with a full-stack debug compound, tasks.json, and per-package settings — all immediately usable. ## Quick Start Ask the assistant to set up VS Code for your monorepo, sharing your directory structure or package.json so it can generate the workspace, debug, and task configuration files.

Frequently Asked Questions about vscode-monorepo-forge

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

FAQPage Schema
How do I set up VS Code for a monorepo?

Create a multi-root .code-workspace file listing each package as a folder, then add files.exclude and search.exclude rules for node_modules and build outputs. This Skill generates the workspace file plus launch.json, tasks.json, and per-package settings adapted to your structure.

How to debug multiple packages at once in VS Code?

Define one launch configuration per app in launch.json, then add a compound configuration that references them by name with stopAll enabled. Starting the compound attaches the debugger to all apps simultaneously, such as a Next.js frontend and Fastify API together.

Does this work with pnpm workspaces and Turborepo?

Yes, the generated configurations assume pnpm as the package manager and include a turbo.json pipeline with build, dev, typecheck, lint, and test tasks. Tasks invoke pnpm turbo commands, and Prisma steps use pnpm --filter to target specific packages.

Why does VS Code search show results from node_modules?

Search includes node_modules when search.exclude rules are missing or when files.exclude hides folders but search settings are not aligned. Add explicit search.exclude entries for node_modules, dist, .next, .turbo, and lockfiles in the workspace settings.

Why is ESLint not resolving per package in a monorepo?

ESLint fails when the extension cannot locate each package's config from the workspace root. Set eslint.workingDirectories to auto mode at the root, or use per-package settings with changeProcessCWD so each package resolves its own configuration.