Menu
Create a GitHub release with a version tag and auto-generated release notes. Does not build artifacts or upload to any store. Use when the user asks to tag a version, create a GitHub release, cut a release, or prepare release notes.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Planner-Generator-Evaluator harness for large, multi-screen features or major refactors. Separates planning, implementation, and evaluation into distinct phases with isolated context, preventing self-grading bias and context drift. Use when the user asks to build a large feature, do a major refactor, or implement something spanning multiple screens/files.
Unified release for both Android and iOS from a single version tag. Runs quality gates, bumps both platform versions in one commit, tags, builds both platforms, uploads Android to Play Store, and opens iOS archive for App Store upload. Use when the user asks to release, ship, cut a release, or make a new version.
Build and upload an Android release based on an existing git tag. Runs lint and all tests first (unit and instrumented), bumps version to match the tag, builds release AAB and APK (without debug info), commits the version bump, and uploads the AAB to Google Play Store internal testing. Use when the user asks to make an Android release, build for Play Store, or upload to Google Play.
Build an iOS release based on an existing git tag. Bumps version to match the tag, builds the shared KMP framework and the iOS app archive. Use when the user asks to make an iOS release, build for App Store, or create an iOS archive.
Add translated strings and plurals to Android and iOS locale files. Use when adding new user-facing strings or plurals, fixing MissingTranslation lint errors, or when the user asks to translate, localize, or add strings to all languages.
Publish the iOS app to Apple's App Store. Covers the full workflow from code signing setup through archive, upload, metadata, and submission. Use when the user asks to publish to App Store, submit for review, upload to App Store Connect, or distribute the iOS app.
| name | github-release |
| description | Create a GitHub release with a version tag and auto-generated release notes. Does not build artifacts or upload to any store. Use when the user asks to tag a version, create a GitHub release, cut a release, or prepare release notes. |
For normal releases, use
/releaseinstead — it creates the tag, bumps both platform versions, builds, and uploads in one workflow. This skill is for creating a tag without building.
Create a version tag on main and a GitHub release with release notes summarizing changes since the previous tag.
gh CLI authenticated (gh auth status)git status shows no uncommitted changes)main branch and up to date with origingit status
git branch --show-current
Confirm the branch is main and there are no uncommitted changes. If the working tree is dirty, stop and ask the user to commit or stash first.
Read the latest existing tag:
git describe --tags --abbrev=0
The project uses semantic versioning (major.minor.patch) with a v prefix (e.g., v9.10.1).
If the user did not specify a version or release type, ask which type of release to create:
| Release type | What changes | Example |
|---|---|---|
| Major | Bump major, reset minor and patch to 0 | 9.10.1 -> 10.0.0 |
| Feature | Bump minor, reset patch to 0 | 9.10.1 -> 9.11.0 |
| Bugfix | Bump patch | 9.10.1 -> 9.10.2 |
Ask the user to confirm the new version before proceeding.
Create an annotated tag on HEAD and push it:
git tag -a v<version> -m "v<version>"
git push origin v<version>
Review commits since the previous tag to build the release notes:
git log <previous-tag>..v<version> --oneline
Summarize the changes into categories (Add, Fix, Update, Refactor, etc.) matching the project's commit format.
Use the gh CLI to create the release. Do not attach any binary files -- binaries are distributed through the Play Store and App Store.
gh release create v<version> \
--title "v<version>" \
--notes "$(cat <<'EOF'
## What's New
- <categorized summary of changes since last release>
EOF
)"
Provide:
v9.11.0)