Android Local Build Manager

Problem

Android local builds often scatter repo paths, branch choices, build commands, and last-run context across machines and notes. Developers may repeatedly reconstruct the same environment or copy shell snippets without a clear project-level history. android-remote-build keeps local build configuration under ~/.android-build, making project settings, generated scripts, and build records easier to reuse.

How It Works

The skill focuses on local Android build configuration with three main capabilities:
- Project configuration: stores project details in ~/.android-build/config.json for later lookup and script generation.
- Build script generation: creates ~/.android-build/scripts/<project>/build.sh so repeated commands become an executable script.
- Build history: writes execution context to ~/.android-build/history/<project>.json for reviewing past builds.

Typical flows start from adding a project, generating its build script, and checking build history. It is useful when the same local build steps need to be repeated without manually reconstructing commands each time.

Boundaries

It is intended for local build configuration and simple script generation, not as a replacement for CI, remote build services, or release pipelines. Because output lives in the user directory, treat repository URLs, branches, and build parameters as sensitive data and avoid sharing unredacted config with others.