android-build-validator

Validates Android Gradle and Rust NDK cross-compilation builds and reports pass or fail verdicts.

Updated May 2, 2026
One-click install
npx skills add https://github.com/whinchman/midi-man-mk3 --skill android-build-validator-whinchman
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: android-build-validator
Source: https://github.com/whinchman/midi-man-mk3/tree/main/.claude/skills/android-build-validator
Command: npx skills add https://github.com/whinchman/midi-man-mk3 --skill android-build-validator-whinchman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Verifying that Android build scripts, Gradle projects, and Rust NDK cross-compilation actually succeed across multiple repos and worktrees is tedious and error-prone when done manually, especially in multi-repo feature workflows. ## Core Features & Use Cases - Automatic Project Detection: Identifies whether a worktree uses a build-android.sh script, Gradle wrapper, or Rust/NDK cross-compilation and runs the appropriate build check. - Multi-Target Rust Cross-Compile: Builds Rust crates for aarch64-linux-android, armv7-linux-androideabi, i686-linux-android, and x86_64-linux-android targets. - Structured Reporting: Writes a Markdown report with a PASS/FAIL verdict table and captured failure output to .workflow/reports/. - Use Case: After implementing a feature spanning multiple repos, run this validator to confirm every affected Android target still compiles before handing off to the coordinator. ## Quick Start Ask the agent to validate all Android builds for the current feature and report whether they pass or fail.

Frequently Asked Questions about android-build-validator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate Android builds across multiple repos automatically?▼

Run the validator against the current feature: it reads task files in .workflow/tasks/, finds Android-related manual steps, resolves each repo's worktree via agent.yaml, and runs the appropriate build check for each target.

How to cross-compile Rust for Android targets?▼

Use cargo build with the --target flag for aarch64-linux-android, armv7-linux-androideabi, i686-linux-android, and x86_64-linux-android. The ANDROID_NDK_HOME environment variable must be set and linker configuration must exist in .cargo/config.toml.

What build types does the Android build validator support?▼

It detects three project types in priority order: a build-android.sh script, a Gradle wrapper (running assembleDebug without signing), or a Cargo.toml requiring Rust/NDK cross-compilation to all four Android targets.

Why does Rust Android cross-compilation fail with linker errors?▼

Failures typically occur when ANDROID_NDK_HOME is unset or .cargo/config.toml lacks linker configuration for Android targets. The validator flags missing linker config for human review rather than creating it automatically.

What happens when no Android build steps are found in a feature?▼

The validator writes a report with the verdict SKIP — no Android manual steps found and stops, so features without Android work do not produce false failures.