skills.rest
mobiustripper42
mobiustripper42COMMUNITY
Explore all skills by this author →
GitHub

bump-major

Bumps the major version in package.json, updates CHANGELOG.md, and tags the release on main.

Updated Aug 25, 2026
Search Tags:#changelog#npm#release#semver#version bump#git tag#breaking change
One-click install
npx skills add https://github.com/mobiustripper42/jig --skill bump-major-mobiustripper42
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bump-major
Source: https://github.com/mobiustripper42/jig/tree/main/.claude/skills/bump-major
Command: npx skills add https://github.com/mobiustripper42/jig --skill bump-major-mobiustripper42

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually releasing a breaking change requires coordinating several error-prone steps: incrementing the major version, documenting the breaking change in a changelog, committing, tagging, and pushing. This Skill automates that entire release sequence while enforcing safety gates so a major bump never lands on the wrong branch or in an unversioned project. ## Core Features & Use Cases - Sanity gating: Verifies the project has a package.json with a version field and that you are on the main branch before making any changes. - Guided version bump: Reads the current version, computes the next major version (e.g. 1.7.3 → 2.0.0), and asks you to confirm and supply a one-line breaking-change rationale. - Changelog and git automation: Prepends a dated BREAKING entry to CHANGELOG.md, commits, creates a vX.Y.Z tag, and pushes both to the remote. - Use Case: You just merged a PR that removes a deprecated API endpoint. Run the skill on main, describe the breaking change, and it produces a tagged v2.0.0 release commit with a proper changelog entry. ## Quick Start Bump the major version of this project and record the breaking change in the changelog.

Frequently Asked Questions about bump-major

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

FAQPage Schema
How do I bump the major version of a Node.js project?▼

Run this skill on the main branch of a versioned project. It reads the current version from package.json, increments the major segment with npm version major, adds a BREAKING entry to CHANGELOG.md, then commits, tags, and pushes the release.

When should I bump the major version instead of minor or patch?▼

Bump the major version for breaking changes: a new data model, a removed feature, or anything users would notice on upgrade. Major bumps are manual because no automatic trigger can determine what counts as breaking.

Can I run a major version bump on a feature branch?▼

No. The skill stops if the current branch is not main, because a bump on a feature branch gets orphaned when the PR merges. Switch to main and re-run the command.

Why does the version bump fail when package.json exists?▼

The gate checks for a version field inside package.json, not just the file's presence. A private, version-less manifest used only for tooling like a test runner is treated as unversioned, and the skill stops without making changes.

Does the version bump create a git tag automatically?▼

Yes. After committing the version and changelog changes, it creates a vX.Y.Z tag on main and pushes both the branch and the tag to the remote. Promotion to a production branch happens separately and does not re-tag.

Related Skills

Explore More Software Engineering Skills→
MohamedSayedKMohamedSayedK

release

Generates a semver release PR with a grouped CHANGELOG entry from conventional commits.

Community
Intermediate
dyoshikawadyoshikawa
1.3k

draft-release

Draft a GitHub release with changelog notes from ./tmp/release-notes/*.md.

Community
Intermediate
IgorGanapolskyIgorGanapolsky
38

Local CI Runner (ACT)

Run GitHub Actions workflows locally in Docker using ACT.

Community
Advanced
marquesfelipmarquesfelip

automated-versioning

Automate semantic version bumps from conventional commits in CI/CD pipelines.

Community
Advanced