Generate a GitHub Actions workflow for Android — JDK + Gradle caching, build, unit + instrumented tests, Android Lint, run the Android pre-flight checks, and (optionally) sign + upload a signed app bundle to a Play track. Use when setting up CI for an Android app.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Generate a GitHub Actions workflow for an Android app. Complements (does not replace)
/sdlc-core:setup-ci — this adds the Android-specific pieces (JDK/Gradle caching, emulators, Play
upload). Belongs to the sdlc-team-android / play-store-release-specialist disciplines.
path-to-android-project — the project directory (defaults to the current directory).Produce an Android CI workflow file under .github/workflows/ with:
ubuntu-latest for build/unit tests; a macOS runner or a Gradle-managed device / AVD
action for instrumented tests. Set JDK 17 (actions/setup-java, temurin).gradle/actions/setup-gradle (caches the Gradle user home + configuration cache);
enable org.gradle.configuration-cache and org.gradle.caching../gradlew assembleDebug testDebugUnitTest lint; instrumented tests via
Gradle-managed devices or reactivecircus/android-emulator-runner. Upload lint/test reports.python -m android_preflight.cli . so config regressions (target-SDK below
the Play minimum, unguarded exported components, missing R8, committed secrets, background-location
without justification) fail CI before a release ever reaches Play.Only if the project releases from CI:
keystore.properties (or pass via env), sign the release —
see android-signing-setup../gradlew bundleRelease → a signed .aab; upload with Gradle Play Publisher,
fastlane supply, or the r0adkll/upload-google-play action to the internal track (draft or
a small inProgress %), then promote after smoke-testing.git rev-list --count HEAD so every CI build is unique, monotonic, and
traceable to a commit.Summarise the workflow: triggers, the test matrix, whether it gates on the pre-flight checker + lint, and whether it uploads to Play. Note any secrets the user must add before it will run.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Validated Google Play release — runs the pre-flight checks and clears the Play policy gates, builds a signed app bundle with a git-stamped versionCode, uploads to a track, and walks staged rollout (with halt/roll-forward). Use when releasing an Android app to Play.
日本語の概要は準備中です。原文の説明を表示しています。
Scaffold a new Android app with SDLC and Play-safe defaults — Kotlin/Compose Gradle project with version catalog, convention plugins, module layout, a targetSdk that meets the Play mandate, R8 on release, and git-ignored signing so it passes the pre-flight checker from day one. Use when starting a new Android project.
日本語の概要は準備中です。原文の説明を表示しています。
Set up Android app signing safely — generate an upload keystore, enroll in Play App Signing, and wire a Gradle release signingConfig that reads secrets from a git-ignored keystore.properties / CI (never committed). Use when configuring signing for a Play release.
日本語の概要は準備中です。原文の説明を表示しています。
Pick an existing workflow for a task or author a new one — recommends workflow + team formation, or generates a fresh workflow YAML with command prompts and team validation.
日本語の概要は準備中です。原文の説明を表示しています。
Guide the team through writing a change-impact record for IEC 62304 / FDA / ISO 26262 ASIL C+ projects. Surfaces the affected REQ/DES/TEST/CODE artefacts and captures human-attested verification approach.
日本語の概要は準備中です。原文の説明を表示しています。
Generate boilerplate `# implements:` annotation for a function based on the artefact ID, inserting it as the first line of the function body.
日本語の概要は準備中です。原文の説明を表示しています。