npm-release

Automate version bumps, changelog updates, and npm publishing for the ai-sdk.

Updated Aug 23, 2026

Search Tags:#automation #git #workflow #versioning #npm #sdk #release

Ready to run

npx skills add https://github.com/eugene-belkovich/ai-setup --skill npm-release

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: npm-release
Source: https://github.com/eugene-belkovich/ai-setup/tree/main/claude/profiles/work/skills/workflow/npm-release
Command: npx skills add https://github.com/eugene-belkovich/ai-setup --skill npm-release

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual SDK version management and publish workflows are error-prone and time-consuming; this skill automates bumps, merges, and npm publishing to ensure consistent releases.

Core Features & Use Cases

Automated version bumps: bump patch, minor, or major versions based on inputs and commit history.
Changelog automation: generate and prepend changelog entries to CHANGELOG.md.
Publish workflow: publish to npm using a token from environment variables with safety checks.
Branch merge support: merge changes through dev and main as part of the release process.

Quick Start

Run the npm-release command with a bump type to automate a release cycle.

Frequently Asked Questions about npm-release

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

FAQPage Schema

How do I automate npm package versioning and publishing for my SDK?▼

Automating npm package versioning involves reading package.json, applying SemVer bumps based on commit history, generating changelog entries, and publishing to npm using an access token. This ensures consistent SDK releases without manual intervention.

What is the best way to maintain a changelog during an SDK release workflow?▼

The best way to maintain a changelog during an SDK release is to automate it. The workflow generates changelog entries based on version bumps and commit history, then prepends them directly to CHANGELOG.md to ensure documentation stays synchronized with releases.

How does branch merging work when publishing an npm release?▼

Branch merging during an npm release involves integrating changes through development and main branches as part of the deployment process. This ensures version updates and changelog modifications are properly propagated across your repository's branch structure before publishing.

Do I need an npm access token to automate SDK publishing?▼

Yes, you need an npm access token to automate SDK publishing. The workflow uses a token provided via environment variables to authenticate with the npm registry, applying safety checks before executing the publish command to ensure secure deployments.

Can I bump major, minor, and patch versions automatically based on commit history?▼

Yes, you can bump major, minor, and patch versions automatically. The workflow evaluates inputs and commit history to determine the appropriate SemVer update level, then modifies the package.json version field accordingly before merging and publishing.