release

Automate repository releases by bumping versions, committing, pushing, and creating GitHub releases.

2|1|Updated May 2, 2026
One-click install
npx skills add https://github.com/iroha924/mumei --skill release-iroha924
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/iroha924/mumei/tree/main/.claude/skills/release
Command: npx skills add https://github.com/iroha924/mumei --skill release-iroha924

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, git, and includes scripts (resource) components.

What problem does it solve?

This Skill automates the release process for a repository, ensuring that new versions are released correctly and consistently, with minimal manual intervention.

Core Features & Use Cases

  • Version Bumping: Automatically bump the version number in the plugin.json file based on user input.
  • Commit and Push: Commit changes, push to the main branch, and watch the CI run.
  • Tag Creation: Create an annotated tag only after the CI run is successful.
  • GitHub Release Page: Create a GitHub Release page with notes generated from the commit messages.
  • Use Case: When you want to release a new version of your repository, you can use this Skill to handle the entire release process with a simple command.

Quick Start

Run the release skill with the desired version number, e.g., /release 0.2.0.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate repository version releases with GitHub?

Automating repository version releases involves bumping version numbers, committing changes, pushing to the main branch, watching CI runs, creating annotated tags, and generating a GitHub release page automatically.

What is the process for bumping a version number and creating an annotated tag?

Bumping a version number and creating an annotated tag requires updating the plugin.json file, committing and pushing changes to the main branch, waiting for CI success, and then creating the annotated tag.

Do I need the gh CLI to automate GitHub release pages?

Yes, you need the gh CLI installed to automate GitHub release pages, alongside git for repository operations like committing changes, pushing to the main branch, and creating annotated tags.

Can I create a GitHub release page only after CI runs are successful?

Yes, you can create a GitHub release page only after CI runs are successful by watching the CI run status and proceeding to create annotated tags and release notes generated from commit messages.

What are the limitations of release automation for repository management?

Release automation for repository management is limited to workflows involving version control and annotated tag creation, relying explicitly on git for operations and gh CLI for GitHub actions.