npm-publisher

Automate npm package releases with version bumps, Git tags, and CI/CD publishing.

181|12|Updated Nov 2, 2025
One-click install
npx skills add https://github.com/klaudworks/universal-skills --skill npm-publisher
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: npm-publisher
Source: https://github.com/klaudworks/universal-skills/tree/main/.agent/skills/npm-publisher
Command: npx skills add https://github.com/klaudworks/universal-skills --skill npm-publisher

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the complexity and potential for errors in manually publishing npm packages. It standardizes the entire release workflow, from version bumping and Git tagging to triggering automated CI/CD, saving developers significant time and ensuring consistent, reliable deployments.

Core Features & Use Cases

  • Automated Release Workflow: Guides you through staging changes, committing, determining the correct semantic version bump (patch, minor, major), and pushing to trigger automated CI/CD.
  • Git & npm Integration: Handles npm version commands, Git commits, and tag pushes seamlessly.
  • CI/CD Verification: Provides steps to verify successful publishing via GitHub Actions and troubleshoot common issues.
  • Use Case: When you've completed a new feature or bug fix, simply activate this skill to flawlessly release your npm package, ensuring correct versioning, Git tagging, and automated deployment to the npm registry.

Quick Start

I need to publish a new minor version of my npm package. Guide me through the release process.

Frequently Asked Questions about npm-publisher

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

FAQPage Schema
How do I automate publishing npm packages to the registry?

Automate npm package publishing by staging changes, committing with semantic versioning (patch, minor, major), running npm version, pushing commits and tags to trigger CI/CD, and verifying successful publication. This Skill handles the entire workflow from Git integration through GitHub Actions deployment to the npm registry.

What's the correct way to bump npm package versions and tag releases?

Determine the version bump type (patch, minor, or major) based on code changes or user input, then use npm version to update package.json and create Git tags automatically. This Skill guides you through the semantic versioning decision and ensures tags are pushed to trigger your CI/CD pipeline.

Can I automate npm releases with GitHub Actions and Git tagging?

Yes. This Skill integrates Git commits, npm version commands, and GitHub Actions to fully automate the release pipeline. It handles staging changes, creating descriptive commit messages, pushing tags, monitoring CI workflows, and verifying npm registry publication without manual intervention.

How do I verify an npm package published successfully after release?

Monitor GitHub Actions workflows to confirm the publish job completes, then verify the new version appears in the npm registry and is installable. This Skill includes verification steps and troubleshooting guidance for common CI/CD and publishing failures.

What should I do before starting an npm package release workflow?

Stage all completed changes in Git, ensure your project uses Git and npm with GitHub Actions configured, and confirm your package.json and versioning strategy are ready. This Skill requires these prerequisites before it can guide you through committing, version bumping, and publishing.

Does this work for patch, minor, and major version releases?

Yes. This Skill handles all three semantic versioning scenarios: patch for bug fixes, minor for new features, and major for breaking changes. It determines the correct bump type from your code diff or accepts user input to ensure accurate version progression.