Agent Skills
› fanfan-de/anybox
› anybox-mobile-release
anybox-mobile-release
GitHub用于在fanfande_studio仓库中准备、验证并发布Anybox Mobile Android应用。遵循mobile-v标签规范，执行版本升级、APK构建、GitHub Release资产生成与上传及最终验证。
Trigger Scenarios
发布移动应用
打包Android客户端
创建GitHub移动发布版
更新版本号
Install
npx skills add fanfan-de/anybox --skill anybox-mobile-release -g -y
SKILL.md
Frontmatter
{
"name": "anybox-mobile-release",
"description": "Prepare, verify, and publish the Anybox Mobile Android app release from the fanfande_studio monorepo using the mobile-v* GitHub Releases flow. Use when the user asks to release, package, publish, update, or document the Anybox mobile\/iPad\/Android client, create mobile GitHub release assets, bump mobile versionCode\/version, or avoid desktop releases interfering with mobile updates."
}
Anybox Mobile Release
Core Rule
Use the mobile-only GitHub Release flow:
- Tags must start with
mobile-v, for examplemobile-v0.2.0. - Release assets must include
anybox-mobile.apkandanybox-mobile-release.json. - Do not use
releases/latestfor mobile update checks; desktop releases can become latest. - The mobile app checks GitHub Releases API and filters only
mobile-v*tags.
Workflow
- Work from the repository root, normally
C:\Projects\fanfande_studio. - Inspect current mobile config in
packages/mobile-app/app.json. - For a native APK release, bump:
expo.versionexpo.android.versionCodewith a strictly increasing integer.
- Build or confirm the APK:
corepack pnpm mobile:android:build:debug - Generate GitHub Release assets:
corepack pnpm mobile:release:github:prepare -- --notes "Release note" - Upload the generated files from
packages/mobile-app/build/github-release/to a GitHub Release whose tag matches the printedmobile-v*tag. - Run verification:
corepack pnpm --filter anybox-mobile-app typecheck corepack pnpm --filter anybox-mobile-app exec expo install --check
Fast Path
Before rebuilding, use the fastest checks to avoid repeating slow work:
- Check whether the existing APK is fresh:
Ifcorepack pnpm mobile:android:delivery-check -- --strict --no-manifestAPK freshnesspasses and the version/tag is still correct, reusepackages/mobile-app/build/anybox-mobile-debug.apk. - On Windows, set the known local toolchain before Android builds:
$env:JAVA_HOME="$env:LOCALAPPDATA\AnyboxMobile\AndroidToolchain\jdk-17" $env:ANDROID_HOME="$env:LOCALAPPDATA\Android\Sdk" $env:ANDROID_SDK_ROOT=$env:ANDROID_HOME $env:ANDROID_NDK_HOME="$env:ANDROID_HOME\ndk\27.1.12297006" $env:ANDROID_NDK_ROOT=$env:ANDROID_NDK_HOME $env:PATH="$env:JAVA_HOME\bin;$env:ANDROID_HOME\platform-tools;$env:ANDROID_HOME\cmdline-tools\latest\bin;$env:PATH" - If Gradle reports a broken NDK such as
ndk\27.0.12077973missingsource.properties, move that incomplete SDK directory out ofAndroid\Sdk\ndkafter verifying it only contains installer residue. - Avoid
--cleanunless generated native files are corrupt. A clean prebuild can add many minutes. Ifprebuildalready producedandroid/andindex.android.bundle, continue with direct Gradle:
Then copy.\gradlew.bat --no-daemon --console=plain assembleDebugandroid/app/build/outputs/apk/debug/app-debug.apktopackages/mobile-app/build/anybox-mobile-debug.apk. - GitHub APK uploads are slow for ~170 MB files. Use long timeouts. If
gh release createtimes out and leaves a draft release, do not recreate blindly; inspect it, upload missing assets withgh release upload, then publish withgh release edit --draft=false.
Decision Points
- For JS/style/business logic only, prefer EAS Update if configured.
- For Android permissions, native dependencies, Expo SDK changes,
android/, or app metadata changes, publish a new mobile APK release. - If the user wants GitHub-only updates, keep EAS project ID unset; mobile APK checks still work through GitHub Releases.
- If publishing is requested and GitHub CLI is available, use the
gh release create ...command printed by the prepare script. Otherwise report the exact files and tag to upload manually.
Reference
Read references/github-mobile-release.md when the task needs exact asset names, manifest fields, release command shape, or troubleshooting details.
Version History
- 08dc189 Current 2026-07-05 18:53
