MF

Streamlines release preparation by automating versioning, changelog updates, and dependency locking.

Install

mkdir -p .claude/skills/mflux-release && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/4636" && unzip -o skill.zip -d .claude/skills/mflux-release && rm skill.zip

Installs to .claude/skills/mflux-release

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Prepare a release in mflux (version bump, changelog, contributors, uv lock) without tagging/publishing. Use when preparing a release branch or release PR.
154 chars✓ has a “when” trigger
Beginner

Key capabilities

  • →Bump project versions in pyproject.toml
  • →Generate changelog entries from commit history
  • →Extract contributor handles from merged PRs
  • →Update uv lockfiles
  • →Prepare release branches

How it works

The skill automates the modification of versioning and documentation files in the repository to prepare for a release PR.

Inputs & outputs

You give it
Release version and commit history
You get back
Updated project files and changelog

When to use mflux-release

  • →Bump project version
  • →Generate release changelog
  • →Update uv lockfile

About this skill

mflux release prep

Releases are prepared in-repo; tagging/publishing is handled by GitHub Actions (release.yml, dispatched from main with the publish confirmation).

How notes work now (#685)

  • Every PR carries a fenced ```release-note block in its body (CI enforces it; none opts a PR out). That block is the only source of release notes.
  • On dispatch, the ungated draft-notes job harvests the blocks for every PR whose squash commit is in previous-tag..HEAD and fills a DRAFT GitHub release, grouped by label.
  • Whoever approves the pypi deployment reads and edits that draft (fixing any [needs edit] lines, adding contributor thanks if wanted); the gated job publishes it exactly as edited. A re-dispatch never overwrites an existing draft; delete the draft to re-harvest.
  • There is no CHANGELOG.md: the notes live in GitHub Releases (https://github.com/mflux-community/mflux/releases).

Release-prep PR checklist

  • Bump version in pyproject.toml
  • Update lockfile: uv lock
  • Release-note block of the prep PR itself: none
  • Prefer one commit named release: prepare <version>
  • Sanity checks (optional unless requested): just test-fast, just build
  • Do not tag releases locally unless explicitly requested (normally handled by CI)

When not to use it

  • →Publishing releases to package registries
  • →Tagging releases locally

Limitations

  • →Requires manual review of commit impact
  • →Contributor data relies on GitHub PR metadata

How it compares

It prepares release metadata and documentation in-repo rather than performing the actual publishing or tagging.

Compared to similar skills

mflux-release side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
mflux-release (this skill)16moNo flagsBeginner
codex-cli-bridge911moReviewIntermediate
code-changelog011moReviewBeginner
dev27moReviewAdvanced

Try saying

Example prompts that trigger this skill in your AI assistant.

Search skills

Search the agent skills registry