agentleFS
kaeawckaeawc/auto-mobile/skills/android-gradlew/SKILL.md

android-gradlew

Skill56 starsChanged 35 days agoApache-2.0View on GitHub

Helper skill for Android-specific validation or build work in the android/ subdirectory; use it when another task needs Gradle wrapper commands run from android/.

  • Pipes a download into a shell
  • Installs packages

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 1 is distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run Android work from android/ via the Gradle wrapper.

    line 8
  2. Very specific:

    Never read or print ~/.gradle/gradle.properties.

    line 13
  3. Very specific:

    Use module-scoped tasks that match the request, for example :junit-runner:test, :playground:app:test or :auto-mobile-sdk:apiDump.

    line 24
  4. Very specific:

    Write long output to scratch/ (the script already does) and read excerpts instead of pasting full logs.

    line 26
  5. Distinctive:

    Treat this as a building-block skill for those, not as the primary workflow when the user asks for a broader task.

    line 34

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Android Gradle Wrapper

Run Android work from android/ via the Gradle wrapper. Never run Gradle tasks from the repo root.

Prerequisites

  • A new worktree needs android/local.properties copied from a working checkout. It is gitignored and Gradle cannot resolve the SDK without it. Never commit it.
  • Never read or print ~/.gradle/gradle.properties; it holds publishing credentials.

Running tasks

  • Default: bash scripts/android/gradlew_task.sh <task> [flags]. It works from any cwd, runs ./gradlew from android/ with the arguments unchanged, and returns Gradle's exit code. Combined stdout and stderr are shown and saved to scratch/gradlew-<UTC timestamp>-<pid>.log; the log path is printed to stderr before and after the run. -h or --help as the first argument prints usage.
  • Modes:
    • Plain (when build-brief is absent, CI is non-empty, or AUTOMOBILE_GRADLEW_NO_BUILD_BRIEF is non-empty): as above, full log shown and tee'd to scratch/.
    • build-brief (when build-brief is on PATH, CI is unset/empty and the opt-out is unset/empty): runs build-brief -- <args> from android/ with BUILD_BRIEF_LOG_DIR=<repo>/scratch. Only build-brief's summary reaches stdout (it prints the raw log path on failure); the wrapper adds no tee and, on a non-zero exit, prints the log directory to stderr. Exit code is Gradle's.
    • Opt out with AUTOMOBILE_GRADLEW_NO_BUILD_BRIEF=1 when you need the full Gradle output.
  • build-brief is optional and third-party. The owner installs it with Homebrew, pinned: brew install static-var/tap/build-brief (pinned version: <VERSION - owner fills in after installing>). Never use a curl | bash installer; agents must not install it.
  • Equivalent without the script: (cd android && ./gradlew <task>).
  • Use module-scoped tasks that match the request, for example :junit-runner:test, :playground:app:test or :auto-mobile-sdk:apiDump.
  • To reproduce CI's Detekt job run the type-resolved detektMain detektTest; a per-module :module:detekt run does not reproduce it.
  • Write long output to scratch/ (the script already does) and read excerpts instead of pasting full logs.

Related skills

  • prepush-android for the fast pre-push smoke check (scripts/prepush-android.sh).
  • validate and test for broader lint, build and test runs.
  • check-ci for exact-head CI logs and artifacts.

Treat this as a building-block skill for those, not as the primary workflow when the user asks for a broader task.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.