npm-release-pipeline

Automate npm package release workflows with validation and git coordination.

3|1|Updated Mar 17, 2026

Search Tags:#automation #git #versioning #npm #release #pipeline #ci

Ready to run

npx skills add https://github.com/cogine-ai/cogine-dev-skillset --skill npm-release-pipeline

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: npm-release-pipeline
Source: https://github.com/cogine-ai/cogine-dev-skillset/tree/main/skills/npm-release-pipeline
Command: npx skills add https://github.com/cogine-ai/cogine-dev-skillset --skill npm-release-pipeline

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Replaces manual, error-prone npm release processes with a safe, repeatable, automated workflow that coordinates versioning, publishing, and release artifacts.

Core Features & Use Cases

Pre-release validation (build, tests, npm pack dry-run), version checks, and changelog handling.
Publish to npm with explicit dist-tag management and verification of published version.
GitHub Release creation and optional closing/labeling of related issues.
Use Case: A repo-agnostic Node.js package ready for publishing to npm after merging to main with a new version.

Quick Start

Run the safe npm release workflow against a repository to publish a new version after all checks pass.

Frequently Asked Questions about npm-release-pipeline

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

FAQPage Schema

How do I automate npm package publishing from a git repository?▼

Automate npm package publishing by validating readiness through prepublish checks, coordinating git tag creation, and executing the npm release with explicit dist-tag management for safe, repeatable workflows.

What is a safe npm release pipeline and how does it prevent bad publishes?▼

A safe npm release pipeline prevents bad publishes by enforcing prepublish checks like build, tests, and pack dry-run, while blocking releases on dirty git worktrees or mismatched package versions.

How do I create GitHub Releases and manage npm dist-tags during a release?▼

Create GitHub Releases and manage npm dist-tags by orchestrating release steps that verify the published version, create git tags, and optionally close or label related issues after publishing.

Can I use this release workflow for any Node.js project defined by package.json?▼

Yes, you can use this repo-agnostic workflow for any Node.js project defined by package.json to handle version checks, changelogs, and release orchestration for release-ready states.

What happens if my git worktree is dirty when I try to publish an npm package?▼

If your git worktree is dirty, the npm release automation prevents publishing to ensure release safety, enforcing a clean repository state before proceeding with version checks and tag creation.

What's the best way to coordinate versioning and changelogs for npm packages?▼

The best way to coordinate versioning and changelogs is using an automated pipeline that handles version checks, validates build and tests, and orchestrates git and npm publishing steps safely.