myco:monorepo-release-engineering

Coordinate multi-package npm release, versioning, and tag workflows.

12|2|Updated Mar 15, 2026

Search Tags:#workspace #monorepo #tagging #release-engineering #ci-publishing #trusted-publishers

Ready to run

npx skills add https://github.com/goondocks-co/myco --skill myco-monorepo-release-engineering

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: myco:monorepo-release-engineering
Source: https://github.com/goondocks-co/myco/tree/main/.agents/skills/monorepo-release-engineering
Command: npx skills add https://github.com/goondocks-co/myco --skill myco-monorepo-release-engineering

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams coordinate and automate release workflows across a multi-package npm workspace, ensuring consistent versioning, publishing, and tag-based deployments for Myco projects.

Core Features & Use Cases

Workspace bootstrap and bootstrap consistency across five packages: @goondocks/myco, myco-team, myco-collective, myco-hub, and myco-shared.
Per-package CI publishing, including tag-driven releases and first-time trusted-publishing bootstrap.
Diagnostics, safeguards, and worktree delivery patterns to prevent silent failures in release pipelines.

Quick Start

Run the monorepo release workflow to bootstrap workspace and publish the first tagged release.

Frequently Asked Questions about myco:monorepo-release-engineering

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

FAQPage Schema

How do I coordinate multi-package npm workspace releases across multiple packages?▼

You coordinate multi-package npm workspace releases by automating versioning, publishing, and tag workflows across the workspace. This ensures consistent tag-driven deployments and prevents silent failures across all published packages in the monorepo.

What is tag-driven release publishing for npm workspace packages?▼

Tag-driven release publishing uses repository tags to trigger per-package CI publishing within an npm workspace. This mechanism automates version updates and deployments for individual packages whenever a new tag is pushed to the repository.

How do I set up trusted publishers for first-time npm package publishing?▼

First-time trusted publishing is bootstrapped during per-package CI publishing setup. This process configures trusted publishers for the package, allowing automated pipelines to publish to npm without requiring manually stored authentication tokens.

Do I need Node 22 to automate monorepo release engineering workflows?▼

Yes, Node 22 is required to run monorepo release engineering workflows. The workspace also requires a root manifest, per-package manifests, and specific wiring steps to properly add and publish new packages.

What are the steps to add a new publishable package to an npm workspace?▼

Adding a publishable package requires four wiring steps and a per-package manifest. This setup integrates the new package into the root workspace manifest, enabling it for CI publishing, tag-driven releases, and workspace bootstrap consistency.

How do worktree delivery gates prevent silent failures in monorepo release pipelines?▼

Worktree delivery gates prevent silent failures in monorepo release pipelines by enforcing diagnostics and safeguards. These gates validate workspace bootstrap consistency and verify publishing states before tag-driven releases finalize.