android-verify
Skill1 starsChanged 19 days agoMITView on GitHub
ARC's Android verification loop — the external verifier for Kotlin/Compose work: zero-warning Gradle build, unit tests, Compose preview screenshot validation, then install and walk the app on a headless emulator with the android CLI. Use after implementing anything on Android, and when the user says "verify the Android build", "does it work on Android", "run the Android tests", "check the emulator", "screenshot the app", "gradlew build", "testDebugUnitTest", "validateDebugScreenshotTest", "headless emulator", "install the APK", "android run", "android layout", "android screen capture". The procedure arc-verify-android runs; the main agent iterates until it is green.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- torisKR/toris-agenttheir own version, first seen Jul 28, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- torisKR/toris-agent★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository5 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- android-doctrineSkill
- android-testing-doctrineSkill
- arc-cli-androidSkill
The file
Files
Android verification loop (ARC Labs)
Your own reading of the diff is never the exit condition — a green step below is. Run from the
project root (where settings.gradle.kts lives). Flags below were verified against
android --help for CLI 1.0.16625370 on 2026-10-21; if android --version differs, re-check
with android <cmd> --help before relying on them (see arc-cli-android).
Preconditions
JAVA_HOME(Android Studio JBR) andANDROID_HOMEset;./gradlewpresent. If not, stop and report — do not install a JDK/SDK on your own.- Flavored projects prefix the variant:
testDevDebugUnitTest,validateDevDebugScreenshotTest. List real task names with./gradlew :app:tasks --allrather than guessing.
The loop
- Build, zero warnings.
./gradlew build— assemble + check. The gates are configured in the build (allWarningsAsErrors, LintwarningsAsErrors, detektmaxIssues: 0), so warnings fail it. Still scan the output: any line startingw:(Kotlin) orWarning:means a gate is misconfigured — report it as a failure, do not call the build clean. Run the project's detekt and ktlint tasks/commands ifbuilddoes not include them. - Unit tests.
./gradlew testDebugUnitTest(or the module-scoped./gradlew :feature:x:testDebugUnitTestwhile iterating, the full task before reporting). Failures: readbuild/reports/tests/andbuild/test-results/. - Screenshot validation.
./gradlew validateDebugScreenshotTest— the visual oracle. Report pathbuild/reports/screenshotTest/debug/(standalone plugin). On AGP test suites the task istest{Suite}{Target}{Variant}TestSuite— seeandroid-skills:testing-setup. Never runupdateDebugScreenshotTestto make validation pass; updating references is a deliberate, user-approved act for an intended visual change. - Emulator.
android emulator list→android emulator start --headless <avd>(returns when booted;--coldto skip the snapshot). No AVD?android emulator create --list-profiles, then ask beforeandroid emulator create <profile>. - Install and launch. Locate the APK:
./gradlew assembleDebug, thenandroid describe --project_dir=.prints the JSON files that map build targets to output artifacts. Thenandroid run --apks=<path/to/app-debug.apk>(add--activity=<name>when the launcher activity is ambiguous).android install --apks=…installs without launching. With more than one device attached, pass--device=<serial>(serials from$ANDROID_HOME/platform-tools/adb devices;android infodoes not list devices). - Inspect.
android layout --pretty(JSON tree:text,content-desc,interactions,bounds,center;--fullfor non-interactive nodes,-o <file>to save) — the primary oracle; it also shows missingcontent-descfor TalkBack. Thenandroid screen capture -o <scratchpad>/screen.pngand look at the PNG before going on. Drive flows withandroid input tap "<selector>",android input text "<text>" "<selector>",android input scroll "<selector>" --dir=down --until="<selector>",android input key back(selectors:text=,id=,class=,desc=plus booleans likeclickable=true). Re-runlayoutafter every action. Elementslayoutcannot find:android screen capture --annotate -o <file>+android screen resolve --screenshot <file> --string "#N". - Clean up.
android emulator stop(pass<avd-or-serial>when several run). Screenshots and layout dumps go to the scratchpad, never the repo.
Re-run from step 1 after every fix. Never report on stale output.
Judging the result
- Fail: build error or any warning, failing test, screenshot diff, crash/ANR on launch,
element missing from
layout, interactive element without a label, clipped/overlapping text, content under system bars (edge-to-edge broken). - Not a failure: transient loading states, intended empty states, disabled controls on an incomplete form.
- Cannot verify here — say so: physical-device-only behavior, Play Billing purchases,
real-account sign-in without provided credentials, Play Console state. Return
⚠️ NEEDS DEVICE VERIFICATIONnaming exactly what to check by hand. A build success is never evidence that something works.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

