flux-release

Synchronize release version numbers across Flux manifest files and generate aligned release notes.

7|1|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/Nairon-AI/flux --skill flux-release
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flux-release
Source: https://github.com/Nairon-AI/flux/tree/main/skills/flux-release
Command: npx skills add https://github.com/Nairon-AI/flux --skill flux-release

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill coordinates and enforces consistency for Flux releases by syncing version numbers across all manifest files and release metadata, preventing drift between published artifacts.

Core Features & Use Cases

  • Bump versions in package.json, .claude-plugin/plugin.json, .claude-plugin/marketplace.json, README badge, and CHANGELOG to keep all artifacts aligned.
  • Create and attach GitHub release notes, tag the release, and prevent stale metadata from drifting from the published tag.
  • Apply during Flux release workflows triggered by /flux:release to ensure a single source of truth for the version.

Quick Start

Invoke the release flow by passing a version, for example '/flux:release v2.5.0'.

Frequently Asked Questions about flux-release

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

FAQPage Schema
How do I synchronize release version numbers across multiple manifest files?

To synchronize release version numbers across manifests, this Skill updates package.json, .claude-plugin files, README badges, and CHANGELOG entries simultaneously to prevent version drift across published artifacts.

How does semver validation work during a GitHub release tag workflow?

Semver validation during a GitHub release enforces semantic versioning rules and tag uniqueness before publishing, ensuring the release tag strictly conforms to versioning standards and preventing duplicate or invalid release tags.

What's the best way to automate version bumps and changelog updates for GitHub releases?

Automating version bumps and changelog updates is handled by triggering the release flow with a target version, which aligns all manifest files and generates matching release notes for the GitHub release automatically.

Why does my package.json version drift from my GitHub release tag?

Version drift between package.json and GitHub release tags occurs when manifest files are updated independently without synchronization, a problem this Skill solves by enforcing a single source of truth across all release artifacts.

Can I use this to generate aligned release notes across multiple artifacts?

Yes, generating aligned release notes across artifacts is a core function that creates consistent release documentation attached to the GitHub release tag while updating the CHANGELOG and manifest files.

Does this release automation workflow require any specific dependencies?

No specific dependencies are required to run this release automation workflow, as it operates independently to validate semver, update manifests, and tag GitHub releases without external package requirements.