mp-release

Bump npm versions, push tags, and verify GitHub Actions runs.

1|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/MartinoPolo/mpx-claude-code --skill mp-release
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mp-release
Source: https://github.com/MartinoPolo/mpx-claude-code/tree/main/_archive/skills-deprecated/mp-release
Command: npx skills add https://github.com/MartinoPolo/mpx-claude-code --skill mp-release

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill reduces the risk and tedium of releasing a new version by automating the steps to bump the project version, create/push the corresponding git tag, and confirm that CI workflows start.

Core Features & Use Cases

  • Determines the bump type: Uses an explicit patch/minor/major argument or asks interactively when missing.
  • Validates release safety: Checks for a clean working tree, verifies an origin remote exists, and warns if the current branch is not main/master.
  • Executes a standard npm-based release: Runs npm version <patch|minor|major> to update version files and create a tag, then pushes tags.
  • Confirms CI activity: Lists recent GitHub Actions runs to show the release workflow was triggered.

Quick Start

Run the Skill with the release type patch, minor, or major to bump the version, push the tag, and verify CI started.

Frequently Asked Questions about mp-release

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

FAQPage Schema
How do I automate npm version bump and git tag push for a new release?

To automate an npm version bump and git tag push, you can use a workflow tool that runs `npm version` with your specified patch, minor, or major input, then pushes the newly created tag to your origin remote.

How can I verify GitHub Actions CI starts after pushing a release tag?

To verify GitHub Actions CI starts after pushing a release tag, you can query recent workflow runs directly to confirm that the release workflow was successfully triggered by the tag push.

What git state is required before cutting an npm release tag?

Before cutting an npm release tag, you need a clean working tree, an existing `origin` remote, and ideally you should be on the main or master branch to ensure release safety.

Does npm version work with GitHub Actions to automatically trigger release workflows?

Yes, `npm version` works with GitHub Actions by creating and pushing a git tag, which triggers the release workflow, allowing you to subsequently list recent runs to confirm CI startup.

What happens if I run a release version bump without specifying patch, minor, or major?

If you run a release version bump without specifying patch, minor, or major, the process will interactively ask you to choose the bump type before executing `npm version` and pushing the tag.