publish-oss

Automate publishing internal monorepo packages as public open source on GitHub and npm.

137|13|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/alexknowshtml/claude-skills --skill publish-oss
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: publish-oss
Source: https://github.com/alexknowshtml/claude-skills/tree/main/publish-oss
Command: npx skills add https://github.com/alexknowshtml/claude-skills --skill publish-oss

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Publishing internal tools as open source carries risks of leaking private references, breaking monorepo synchronization, or failing npm authentication, and this skill eliminates those manual errors with a guided end-to-end checklist.

Core Features & Use Cases

  • Private Reference Scrubbing: Automatically scans documentation and code for internal tool names, private packages, localhost URLs, and hardcoded personal paths, proposing public replacements before publishing.
  • Full Publishing Pipeline: Handles GitHub repo creation or updating, dist build verification, semantic version bumping, npm publishing with granular token authentication, and bi-directional monorepo syncing.
  • Use Case: A developer with an internal CLI tool in their company's monorepo can use this skill to safely publish it as a public npm package with a standalone public GitHub repository, no manual guesswork required.

Quick Start

Use the publish-oss skill to publish the internal package located at ./packages/internal-api-client as a public open source package on npm and GitHub, ensuring all private internal references are removed before publishing.

Frequently Asked Questions about publish-oss

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

FAQPage Schema
How do I safely publish an internal monorepo package to npm without leaking private references?

To safely publish an internal monorepo package to npm, you must scan code and documentation for private tool names, localhost URLs, and hardcoded paths, replacing them with public alternatives before running the npm publish workflow.

What is the best way to sync a standalone public GitHub repository with an internal monorepo package?

The best way to sync a standalone public GitHub repository with an internal monorepo is using git subtree syncing, which maintains bi-directional synchronization between the linked repositories during the open-source publishing process.

Can I automate semantic version bumping for a single package inside a monorepo before publishing to npm?

Yes, you can automate monorepo-safe semantic version bumping for a single package before publishing to npm, ensuring the version increment applies only to the targeted package without disrupting the broader monorepo dependencies.

Does publishing open source tools from a monorepo require granular npm token authentication?

Publishing open source tools from a monorepo requires granular npm token authentication to securely scope publication rights, preventing unauthorized access to your npm account while automating the end-to-end release pipeline.

Why do I need to verify the dist build before publishing an internal CLI tool as a public npm package?

You need to verify the dist build before publishing an internal CLI tool to ensure the compiled output is valid and functional, preventing broken public package releases and ensuring the open-sourced tool works independently of the monorepo.