bmad-os-release-module

Coordinate software releases with version bumps, changelog updates, git tagging, npm publishing, and GitHub release creation.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/GenEducation/GenedUIProject --skill bmad-os-release-module-geneducation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-os-release-module
Source: https://github.com/GenEducation/GenedUIProject/tree/main/.gemini/skills/bmad-os-release-module
Command: npx skills add https://github.com/GenEducation/GenedUIProject --skill bmad-os-release-module-geneducation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the manual coordination required to ship a software release by guiding version changes, changelog updates, tagging, publishing, and release creation in a controlled sequence.

Core Features & Use Cases

  • Release Orchestration: Verifies the repository state, checks for unpushed work, and walks through each release step in order.
  • Version and Changelog Management: Collects or confirms release notes, updates the changelog, and applies the requested semantic version bump.
  • Publishing and Distribution: Handles git tagging, npm publishing, and GitHub release creation for a complete release handoff.
  • Use Case: A maintainer preparing a package release can use this Skill to ensure the version, changelog, tag, package publish, and GitHub release all stay aligned.

Quick Start

Ask the Skill to perform a release for the project path you want to ship and provide the changelog details when prompted.

Frequently Asked Questions about bmad-os-release-module

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

FAQPage Schema
How do I automate npm publishing and git tagging for a package release?

Automate npm publishing and git tagging by orchestrating a controlled release sequence that applies version bumps, updates changelogs, creates git tags, publishes to npm, and generates GitHub releases with explicit failure handling.

What is the safest way to update a changelog and create a GitHub release?

The safest changelog update and GitHub release method involves verifying a clean working tree, validating versions, reviewing changelog details, and executing release steps sequentially with user confirmation before distribution.

Does this release workflow require a clean git working tree before publishing?

Yes, release orchestration requires a clean git working tree and checks for unpushed work before proceeding with version validation and npm publishing to ensure repository state integrity.

How do I run a semantic version bump and npm publish without manual errors?

Run a semantic version bump by guiding the repository through sequential release execution, applying version changes, updating the changelog, tagging, and publishing with explicit failure handling at each step.

Can I use this release orchestration for repositories without GitHub CLI installed?

No, GitHub CLI is required for release creation. The orchestration handles GitHub release creation using the GitHub CLI, alongside npm publishing and git tagging, requiring it for complete release handoff.

What happens if the npm publish step fails during the release sequence?

If npm publish fails, explicit failure handling stops the release sequence. The orchestration executes release steps in order with user confirmation, preventing subsequent GitHub release creation when publishing errors occur.