publish-package-cicd

Automate secure npm publishing in monorepos with Changesets and OIDC.

1|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/ImBIOS/swarm-tools --skill publish-package-cicd-imbios
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: publish-package-cicd
Source: https://github.com/ImBIOS/swarm-tools/tree/main/.opencode/skill/publish-package-cicd
Command: npx skills add https://github.com/ImBIOS/swarm-tools --skill publish-package-cicd-imbios

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Automated, secure npm publishing for monorepos by integrating Changesets with npm Trusted Publishers (OIDC), removing the need for manual tokens and reducing release toil.

Core Features & Use Cases

  • Manual changeset creation and version bumps drive automated release PRs in CI.
  • Automated publish flow via a Changesets workflow, including changelog generation and workspace:* resolution before publish.
  • OIDC-based publishing in CI without NPM_TOKEN, using tarballs produced by bun pm pack.

Use cases include releasing multiple packages in a tight monorepo setup, maintaining changelogs, and ensuring secure, tokenless publication across environments.

Quick Start

Configure a Changesets-based release workflow and push a minimal changeset file to trigger automated publishing via OIDC.

Frequently Asked Questions about publish-package-cicd

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

FAQPage Schema
How do I automate npm publishing in a monorepo without using an NPM_TOKEN?

Automated npm publishing in a monorepo without an NPM_TOKEN is achieved by integrating Changesets with npm Trusted Publishers using OIDC. This removes manual token management by relying on identity-based authentication directly within your CI workflow.

What is the best way to resolve workspace dependencies when publishing monorepo packages?

The best way to resolve workspace dependencies during monorepo packaging is by using bun pm pack to generate tarballs. This ensures workspace:* references are correctly resolved before packages are published to the registry.

How do Changesets generate release notes for multiple packages in a CI workflow?

Changesets generate release notes for multiple packages by consuming manual changeset files created during development. These files drive automated version bumps and changelog generation within the CI release workflow.

Do I need to configure npm Trusted Publishers to use OIDC for publishing?

Configuring npm Trusted Publishers in your repository settings is required to use OIDC for publishing. This setup allows the CI environment to securely publish packages without needing a manually configured NPM_TOKEN.

Can I use this Changesets workflow if my monorepo does not use bun for packing?

A bun-based packing process is explicitly required for this workflow to resolve workspace dependencies and produce tarballs. Monorepos not utilizing bun for packaging will need to adapt their environment to support this specific flow.