Menu
Create a new release. Bumps version, updates changelog, creates fastlane changelog, commits, tags, and pushes.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
| name | release |
| description | Create a new release. Bumps version, updates changelog, creates fastlane changelog, commits, tags, and pushes. |
| allowed-tools | Read, Edit, Write, Bash, Glob |
Create a new release for MateDroid.
main branch with no uncommitted changes[Unreleased] section in CHANGELOG.md has content to releaseAsk the user what type of release:
Edit app/build.gradle.kts:
./scripts/bump-version-code.sh to generate a new monotonic versionCode (epoch/10). The script updates build.gradle.kts in-place and prints the new code to stdout.versionName to the new version## [Unreleased] to ## [X.Y.Z] - YYYY-MM-DD (today's date)## [Unreleased] section above it[X.Y.Z]: https://github.com/vide/matedroid/compare/vPREVIOUS...vX.Y.Z
[Unreleased] link to compare from the new versionCreate fastlane/metadata/android/en-US/changelogs/{versionCode}.txt with the release notes.
Important — stable vs beta scope:
1.1.0-beta2): the changelog covers only the changes since the previous release (beta or stable).1.1.0): the changelog must cover all changes since the previous stable release (e.g. 1.0.0), NOT just what changed since the last beta. Collect entries from every intermediate beta and the [Unreleased] section, then write a single consolidated changelog. This is what end-users on the production track will see — they never saw the beta changelogs.
Format (max 500 chars for Play Store):
More human readable and engaging new features and major fixes overview. Do NOT mention external contributors here.
Added:
- Feature 1
- Feature 2
Changed:
- Change 1
Fixed:
- Fix 1
Keep it concise - this appears in Play Store and F-Droid. Make the opening text engaging without it being too verbose or showy.
Remember, the fastlane changelog MUST BE less than 500 characters long.
Automatically translate the English changelog and write the translations to:
fastlane/metadata/android/it-IT/changelogs/{versionCode}.txt (Italian)fastlane/metadata/android/es-ES/changelogs/{versionCode}.txt (Spanish)fastlane/metadata/android/ca-ES/changelogs/{versionCode}.txt (Catalan)fastlane/metadata/android/zh-CN/changelogs/{versionCode}.txt (Chinese Simplified)Do this immediately after creating the English changelog - no user interaction needed.
Translation guidelines:
All the changelogs in fastlane, for any language, MUST BE LESS THAN 500 characters. ALWAYS check with wc how long they are.
git add -A
git commit -m "chore: release vX.Y.Z"
git tag -a vX.Y.Z -m "Release X.Y.Z"
git push origin main
git push origin vX.Y.Z
Use gh release create vX.Y.Z --title "vX.Y.Z" --notes-file - with the changelog content as the one in Fastlane.
Mention external contributors, highlighting new ones and giving credit.
The GitHub Actions workflow will automatically:
-beta releases, production track for stable releases)Fix a GitHub issue following the standard workflow. Reads the issue, creates a branch/PR, applies the fix, runs tests, and merges when CI passes.
Add a new translatable string to all locale files (English, Italian, Spanish, Catalan, German, Chinese). Use when adding user-visible text to the app.
Start the Teslamate API mock server to test car image rendering with different vehicle configurations. Takes a description of the car to mock. Can also simulate charging sessions (AC/DC).
Implement a new feature following the standard workflow. Explores the codebase, creates a plan, implements the feature, runs tests, creates a PR, and installs on the connected device.
Check Teslamate API response format for a given endpoint. Use when you need to understand the JSON structure returned by the API.
Scaffold a new Jetpack Compose screen following project patterns. Use when creating a new screen or view in the app.