companion-packages

Resolve brepjs monorepo package structure, build order, and release pipeline issues.

77|7|Updated Feb 1, 2026
One-click install
npx skills add https://github.com/andymai/brepjs --skill companion-packages
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: companion-packages
Source: https://github.com/andymai/brepjs/tree/main/.claude/skills/companion-packages
Command: npx skills add https://github.com/andymai/brepjs --skill companion-packages

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Working in the brepjs monorepo often leads to confusion about which package serves what purpose, why build or npm errors occur, how to order tasks correctly, and how to safely add or modify workspace packages without breaking the release pipeline or CI.

Core Features & Use Cases

  • Full package map: Clear reference for all 9 monorepo packages and 2 apps, including their publish status, purpose, and tier (published satellite, source-shipped internal, private).
  • Error troubleshooting: Step-by-step fixes for common issues like npm ETARGET errors, stale playground builds, missing WASM files, Dependabot alerts on wildcard dependencies, and failed manual publishes.
  • Build and release guidance: Explicit build order for all common workflows (playground, full site, brepjs-cad) and clear rules for the release-please managed publish pipeline.
  • New package checklist: Step-by-step guidance for adding new workspace packages, including tier selection, dependency setup, CI configuration, and release pipeline integration. Use case: If you are editing brepjs-bim and notice the playground is showing stale behavior, or npm ci fails with an ETARGET error after merging a leaf release PR, this skill gives you the exact root cause and fix.

Quick Start

Use the companion-packages skill to resolve the npm ETARGET error you are seeing after editing a brepjs workspace package and pushing a change.

Frequently Asked Questions about companion-packages

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

FAQPage Schema
How do I fix npm ETARGET errors in a brepjs monorepo workspace after merging a release PR?

Fix npm ETARGET errors in a brepjs monorepo by checking workspace dependency versions and updating the root lockfile. This skill identifies the leaf release PR mismatch and provides the exact root cause and resolution steps.

What is the correct build order for brepjs-cad and the full site in an npm workspaces monorepo?

The correct build order for brepjs-cad and the full site requires following explicit workflow sequences to prevent stale playground outputs. This skill provides the exact build ordering rules for all common monorepo build paths.

How do I add a new workspace package to a JavaScript CAD monorepo without breaking the release pipeline?

Add a new workspace package safely by selecting the correct tier, configuring dependencies, setting up CI, and integrating release-please. This skill provides a step-by-step checklist to ensure release pipeline stability.

Why does the brepjs playground show stale behavior after editing a workspace package?

The brepjs playground shows stale behavior when workspace builds are ordered incorrectly or WASM files are missing. This skill traces the build workflow error and provides troubleshooting steps to refresh the playground correctly.

How does the release-please publish pipeline work for npm workspace packages?

The release-please pipeline manages publishing by enforcing strict rules for published satellite, source-shipped internal, and private packages. This skill outlines the exact publish rules and pipeline adherence requirements.

How do I resolve Dependabot alerts on wildcard dependencies in an npm workspaces monorepo?

Resolve Dependabot alerts on wildcard dependencies by pinpointing the specific workspace package versions causing the mismatch. This skill provides targeted CI troubleshooting steps for monorepo dependency failures.