publish-oss

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.