release

Name: release
Availability: InStock
Author: Birdgg

Automate moe-bangumi releases with semver validation, changelog generation, and Git tags.

2|Updated Nov 17, 2025

Search Tags:#automation #git #changelog #versioning #release #semver

Ready to run

npx skills add https://github.com/birdgg/moe-bangumi --skill release-birdgg

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release
Source: https://github.com/birdgg/moe-bangumi/tree/main/.agents/skills/release
Command: npx skills add https://github.com/birdgg/moe-bangumi --skill release-birdgg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create a streamlined, error-resistant release workflow by automating versioning, changelog generation, and publishing.

Core Features & Use Cases

Supports explicit version input or auto-detection from conventional commits
Validates semver, updates moe-bangumi.cabal, and generates CHANGELOG.md
Creates git tags and pushes to origin, coordinating with CI actions for publishing artifacts

Quick Start

Ask the AI to create a new release by providing a version or requesting auto-detection.

Frequently Asked Questions about release

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

FAQPage Schema

How do I automate git release versioning and changelog generation from conventional commits?▼

To automate git release versioning and changelog generation, you can use a workflow that auto-detects version changes from conventional commits, applies semver rules, updates your configuration file, and generates CHANGELOG.md automatically.

What is the process for creating a git tag and pushing it to origin during a release?▼

Creating a git tag and pushing it to origin during a release involves performing pre-release checks, updating configuration files, committing changes, creating the tag, and pushing everything to origin to trigger optional CI publishing actions.

Can I explicitly specify a version number instead of relying on auto-detection from commits?▼

Yes, you can explicitly specify a version number instead of using auto-detection from commits, allowing you to override the automatic semver bumping and directly input the desired version for validation and publishing.

Does the release workflow validate semver rules and check for existing tags?▼

The release workflow validates semver rules and checks for existing tags to ensure version integrity, preventing duplicate tags and ensuring the proposed version number strictly follows semantic versioning standards before committing.

What's the best way to update moe-bangumi.cabal and publish builds in a single release?▼

The best way to update moe-bangumi.cabal and publish builds in a single release is using an end-to-end automation workflow that updates the configuration, commits changes, creates git tags, pushes to origin, and coordinates with CI actions to publish artifacts.

Are there limitations when using conventional commits for auto-detecting release versions?▼

When using conventional commits for auto-detecting release versions, limitations include the reliance on strict commit message formatting; if messages deviate from conventions, the semver auto-detection may fail or require explicit version input instead.