# Mp Release

> Bump version, push tag, verify CI workflow starts. Use when: "release", "bump version", "version bump", "cut a release"

- Skill: `martinopolo/mp-release` (Agent Skill)
- Install (CLI): `npx skillmds@latest add martinopolo/mp-release`
- Raw SKILL.md: https://api.skillmd.com/api/skills/martinopolo/mp-release/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: MartinoPolo (https://skillmd.com/u/martinopolo)
- Updated: 2026-09-10
- Page: https://skillmd.com/skills/martinopolo/mp-release

---


# Version Bump + Release

Bumps version, pushes tag, verifies CI workflow starts. $ARGUMENTS

## Workflow

### Step 1: Detect Project Type

- `manifest.json` exists → Obsidian plugin
- `package.json` only → npm package

### Step 2: Show Current Version

Read version from `package.json` (and `manifest.json` if Obsidian plugin). Display to user.

### Step 3: Get Bump Type

If `$ARGUMENTS` contains patch/minor/major, use it. Otherwise ask:

```
AskUserQuestion: "What type of version bump?"
Options: patch, minor, major
```

### Step 4: Verify Clean Working Tree

Run `git status --porcelain`. If output non-empty, warn user about uncommitted changes and ask to continue or abort.

### Step 5: Check Remote

Run `git remote get-url origin`. Fail if no remote configured.

### Step 6: Check Branch

Run `git branch --show-current`. Warn if not on main/master — releases should typically come from the main branch.

### Step 7: Run Version Bump

```bash
npm version <patch|minor|major>
```

This triggers the `version` script in package.json (e.g., `version-bump.mjs` for Obsidian plugins), commits the version change, and creates a git tag.

### Step 8: Push with Tags

```bash
git push --follow-tags
```

### Step 9: Verify Workflow Started

```bash
gh run list --limit 3
```

Show recent workflow runs to confirm the release workflow triggered.

### Step 10: Summary

Report: new version number, tag created, workflow status.