publish-repo

Automate npm package releases with version bumps, changelog updates, build, test, and publish.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/kitfunso/omniskill --skill publish-repo-kitfunso
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: publish-repo
Source: https://github.com/kitfunso/omniskill/tree/main/skills/publish-repo
Command: npx skills add https://github.com/kitfunso/omniskill --skill publish-repo-kitfunso

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ship an npm package release end-to-end, handling version bumps across manifests, updating CHANGELOG and README, building, testing, committing, tagging, publishing to npm, and pushing changes.

Core Features & Use Cases

  • End-to-end release workflow for npm packages, including version bumping, changelog updates, and manifest synchronization.
  • Build, test, commit, tag, and publish to npm with optional global installation.
  • Supports common release scenarios (patch/minor/major) and user-specified versions, plus safe verification steps.

Quick Start

Initiate the release workflow from the project root to bump the version, update changelogs, build, test, and publish.

Frequently Asked Questions about publish-repo

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

FAQPage Schema
How do I automate npm package releases including version bumps, testing, and publishing?

You can automate npm package releases end-to-end by bumping versions across manifests, updating CHANGELOG and README, building, testing, committing, tagging, publishing, and pushing changes in a single workflow.

What is the best way to bump versions across multiple manifests for a Node.js release?

Bumping versions across manifests requires manual synchronization rather than relying on npm version. This approach ensures your package.json and related files stay aligned before committing and tagging your release.

Can I publish pre-release versions of my npm package using an automated workflow?

Yes, the automated npm publish workflow supports patch, minor, and major version bumps, as well as pre-releases. It applies to any Node.js project with a package.json and typical release workflows.

Does the release workflow run tests before publishing to the npm registry?

Yes, the workflow ensures build and tests pass before publishing to npm. This safe verification step prevents broken or failing packages from being released to the registry.

How do I trigger an end-to-end npm release from my project root?

Initiate the release workflow from the project root to start the sequence of version bumping, changelog updates, building, testing, and finally publishing to npm with optional global installation.

What are the limitations of using manual version bumps instead of npm version for releases?

Manual version bumps require you to update versions across all manifests yourself without the npm version command. You must ensure synchronization manually, but this provides stricter control over your release management process.