thomasrohde/mdvw · Archived

cut-release

Cut a release atomically — bump version, date the CHANGELOG section, commit, tag. Invoke with /cut-release X.Y.Z.

First seen Jun 22, 2026

Installation

$ npx skills add thomasrohde/mdvw --skill cut-release

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from thomasrohde/mdvw.

npx skills add thomasrohde/mdvw

Browse all from thomasrohde/mdvw

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 2
License LICENSE
Default branch main
Open issues 2
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,194 B
  • docs SUMMARY.md 134 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

Version to release: $ARGUMENTS.

Preflight:

  1. git status --porcelain — must be empty. If not, stop and tell the user.
  2. python -c "import mdvw; print(mdvw.version)" — must end in .devN. If not, stop and tell the user to run --post-release first or amend manually.
  3. Confirm ## [Unreleased] in CHANGELOG.md has real notes (not just the placeholder comment). If it looks empty, ask the user to confirm before proceeding.

Then run the /verify skill — don't cut a release on a failing tree.

If all green, run:

python scripts/release.py $ARGUMENTS

Report the resulting commit SHA and tag. Then print the push command verbatim for the user to run:

git push origin main v$ARGUMENTS

Do not push automatically. The tag push triggers release.yml which publishes to PyPI — that's a decision for the user.

After they've pushed (and the release has landed), suggest:

python scripts/release.py --post-release <next>.dev0

to reopen the dev cycle.