Android Pre-push Smoke Check
SkillDev toolsRun the fast Android pre-push smoke check for changed Kotlin modules, then interpret emulator CI failures from boot diagnostics before treating them as regressions.
Use Android Pre-push Smoke Check in Claude, ChatGPT or Ahel Desktop
Free. Sign in, add Android Pre-push Smoke Check and connect your AI. About a minute.
Also: Claude Code · Cursor · Codex
Then ask your AI: use the Android Pre-push Smoke Check skill
Details
Instructions available. Your AI can read the instructions. Execution depends on the setup they require.
Account requirements not reviewed. Check the skill instructions before use; Ahel provides instructions and does not run this skill.
No other account needed.
Add Ahel to your AI once: Claude, ChatGPT, Cursor, Claude Code or Codex. Then ask it to use this.
What this skill tells your AI
The instructions your AI receives, as published by kaeawc/auto-mobile in skills/prepush-android/SKILL.md and read by Ahel’s review.
- Run
scripts/prepush-android.shfrom the repository root before pushingandroid/changes. - Treat its scoped Detekt result as a local smoke check, not a replacement for CI's full-tree Detekt job.
- Copy
android/local.propertiesfrom a working checkout into a new Android worktree before Gradle work. - For Playground or JUnit-runner emulator CI red, inspect
.github/actions/android-emulatorboot diagnostics first: missing runner-health means infra/runner readiness, while a booted emulator with failed tests is a regression. - Use
android-gradlewfor targeted Gradle validation andcheck-cifor exact-head CI logs and artifacts.
Signals
- GitHub stars
- 51
- Forks
- 7
- Last commit
- Oct 2026
Advanced
- Item type
- skill
- Key
prepush-android- Source
- github.com/kaeawc/auto-mobile