release

Automates versioned releases by updating changelogs, bumping versions, tagging, and pushing to git.

548|29|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/hacan359/tonkatsu_box --skill release-hacan359
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/hacan359/tonkatsu_box/tree/main/.claude/skills/release
Command: npx skills add https://github.com/hacan359/tonkatsu_box --skill release-hacan359

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Releasing a new app version involves many error-prone manual steps: analyzing commits, choosing a SemVer bump, updating CHANGELOG.md and pubspec.yaml, writing bilingual release notes, creating F-Droid changelogs, and tagging in git. This Skill orchestrates the entire release pipeline so nothing is forgotten. ## Core Features & Use Cases - Change Analysis & Version Suggestion: Scans commits since the last tag and the [Unreleased] CHANGELOG section, then suggests a SemVer bump (patch/minor/major) with reasoning and asks for confirmation. - Multi-File Version Propagation: Updates CHANGELOG.md, pubspec.yaml (version+build number), the landing page docs/index.html, the in-app assets/whats_new.md dialog, and creates fastlane/metadata/android/en-US/changelogs/N.txt for IzzyOnDroid/F-Droid. - Bilingual Release Notes & Git Tagging: Generates user-facing English and Russian release notes, commits all changes, creates an annotated git tag with the notes, and pushes to trigger the CI release workflow. - Use Case: After merging features for a Flutter app, run the release process to go from a clean working tree to a pushed v0.10.0 tag with GitHub Actions building Windows and Android artifacts automatically. ## Quick Start Run the release process to analyze my changes since the last tag, suggest a new version, update all changelogs, and push the release tag.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate a release with changelog and git tag?

Run the release process with a clean working tree. It analyzes commits since the last tag, suggests a SemVer version bump, updates CHANGELOG.md and pubspec.yaml, generates release notes, then commits, creates an annotated tag, and pushes to trigger CI.

How is the next version number determined for a release?

The version follows pre-1.0 SemVer rules: patch for bug fixes, minor for new features, major for stable or breaking releases. The build number is calculated as the count of existing v* git tags plus one, appended to pubspec.yaml as X.Y.Z+N.

Does this release process work with F-Droid or IzzyOnDroid?

Yes, it creates fastlane/metadata/android/en-US/changelogs/N.txt where N is the build number. The file is plain text under 500 characters, which IzzyOnDroid displays as the per-version What's New entry.

What happens if the working tree is dirty before a release?

The process stops immediately during preflight checks and instructs you to commit or stash changes first. A clean working tree is a hard prerequisite to prevent uncommitted work from being mixed into the release commit.

Why is my in-app What's New dialog not showing after an update?

The dialog reads assets/whats_new.md and only displays the section whose heading exactly matches the app version. If the file was not overwritten with the new version heading during release, the dialog silently never appears.