omcustom:npm-version

Bump npm package versions and update package.json and CHANGELOG.md.

13|6|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/baekenough/second-brain --skill omcustom-npm-version
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: omcustom:npm-version
Source: https://github.com/baekenough/second-brain/tree/main/.claude/skills/npm-version
Command: npx skills add https://github.com/baekenough/second-brain --skill omcustom-npm-version

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manage semantic versioning for npm packages with integrated changelogs and Git workflow.

Core Features & Use Cases

  • Bump major, minor, or patch versions and update package.json automatically.
  • Generate and update CHANGELOG.md, commit changes, and optionally create Git tags.
  • Use in release workflows including release branches, with guardrails for clean working directories and consistent versioning.

Quick Start

Run npm-version patch to bump the patch version and propagate the changes.

Frequently Asked Questions about omcustom:npm-version

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

FAQPage Schema
How do I automate npm package version bumps and update the changelog?

Semantic versioning for npm packages tracks major, minor, and patch increments to communicate breaking changes, new features, and fixes. This Skill automates reading the current version, computing the bump, and updating package.json and CHANGELOG.md.

How do I create Git tags when releasing a new npm package version?

Yes, this Skill applies version increments across both libraries and applications, computing major, minor, and patch bumps while updating package.json and CHANGELOG.md for each release.

Do I need a clean Git working directory before bumping an npm package version?

This Skill automates semantic versioning by reading the current version, computing the specified major, minor, or patch bump, updating package.json and CHANGELOG.md, and generating a Git commit with optional tagging.

Does this npm versioning workflow support release branches?

You can bump the npm package version by running a command like npm-version patch, which computes the increment, updates package.json and CHANGELOG.md, creates a commit, and optionally tags the release.