release-engineering

Automate Android version bumps, APK builds, and git release tagging.

Updated Apr 18, 2026
One-click install
npx skills add https://github.com/hiroshiyui/LowBudgetVoiceRecognitionInput --skill release-engineering-hiroshiyui
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-engineering
Source: https://github.com/hiroshiyui/LowBudgetVoiceRecognitionInput/tree/main/.claude/skills/release-engineering
Command: npx skills add https://github.com/hiroshiyui/LowBudgetVoiceRecognitionInput --skill release-engineering-hiroshiyui

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Release engineering tasks for the Low Budget Voice Recognition Input Android app, including version bumps, release APK builds, tagging, and changelog creation to prepare distributions.

Core Features & Use Cases

  • Version bumps in app/build.gradle.kts to reflect new releases.
  • Build pipelines for debug and release APKs using Gradle tasks.
  • Tag releases in git and generate changelogs for distribution channels.

Quick Start

Bump the version, build the release APK, and tag the release.

Frequently Asked Questions about release-engineering

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

FAQPage Schema
How do I automate Android release builds and versioning?

Automate Android release builds and versioning by bumping versions in app/build.gradle.kts, running Gradle tasks to build release APKs, tagging git commits, and generating changelogs for distribution.

What's the best way to bump an Android app version and create a release tag?

Bump an Android app version and create a release tag by modifying app/build.gradle.kts and using git to tag the release. This prepares the distribution pipeline and ensures version tracking for the release APK.

Do I need Gradle scripts and git access to build a release APK?

Yes, you need Gradle scripts and git access to build a release APK. The release engineering process requires modifying app/build.gradle.kts, running Gradle build tasks, and tagging releases in the local git repository.

Can I generate a changelog automatically when tagging an Android release?

Yes, you can generate a changelog automatically when tagging an Android release. The workflow covers pre-release validation and creates changelog documentation for distribution channels alongside the git tag and release APK build.

Why does my Android release workflow require build validation?

Android release workflows require build validation to ensure the release APK is correctly compiled and versioned before distribution. This prevents deploying faulty builds by checking the Gradle output before tagging the git release.