agentleFS
Sign inStart free
osocietyosociety/vernet/.github/skills/android-fastlane-release/SKILL.md

android-fastlane-release

Skill566 starsChanged 14 days agoApache-2.0View on GitHub

Build or troubleshoot Vernet Android release and beta delivery with Fastlane, Play Console supply, signing configuration, Gradle, or release CI.

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 5 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this for Android release builds, Fastlane lanes, Google Play beta/internal tracks, signing failures, and release automation in CI.

    line 9
  2. Very specific:

    Verify the installed Fastlane/Ruby/Gradle context and supported lane options before changing dependency versions or command flags.

    line 15
  3. Distinctive:

    When preparing a release:

    line 22
  4. Very specific:

    Create changelog at android/fastlane/metadata/android/en-US/changelogs/<version_code>.txt

    line 24
  5. Very specific:

    Do not create a root CHANGELOG.md file.

    line 26
  6. Distinctive:

    Check for pre-existing edits before touching release files and leave them intact.

    line 31
  7. Distinctive:

    Avoid broad dependency updates when a targeted version or configuration fix is sufficient.

    line 32
  8. Distinctive:

    Never claim a release succeeded based only on a successful build.

    line 33

≈ “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 Fastlane Release

Use this for Android release builds, Fastlane lanes, Google Play beta/internal tracks, signing failures, and release automation in CI.

Procedure

  1. Determine the requested outcome: diagnose a failed lane, prepare a local build, or publish to a specific track. Do not infer authorization to upload or deploy from a request to investigate or build.
  2. Inspect the Android Fastlane Fastfile, Gemfile and lockfile, Gradle configuration, and the relevant GitHub Actions workflow. Read the exact failing lane output and identify whether the failure is build, signing, authentication, upload, or Play Console state.
  3. Verify the installed Fastlane/Ruby/Gradle context and supported lane options before changing dependency versions or command flags. Keep local and CI configuration differences explicit.
  4. Preserve the project’s existing signing setup. Use key and service-account paths or secret names only; never read out or expose secret contents. Do not hardcode credentials, package IDs, or production values into committed files for convenience.
  5. Make the smallest fix, then validate with a local build or the narrowest non-publishing lane available. If upload is needed, state the target track and obtain explicit user authorization before executing it.
  6. Summarize the root cause, files changed, exact validation run, and whether the artifact was built or actually uploaded.

Release Preparation

When preparing a release:

  • Bump version in pubspec.yaml (format: major.minor.patch+version_code)
  • Create changelog at android/fastlane/metadata/android/en-US/changelogs/<version_code>.txt
  • Changelog format: concise, user-friendly lines (one feature/fix per line, no markdown, no version header)
  • Do not create a root CHANGELOG.md file; fastlane structure is the source of truth
  • iOS and Android read versions from pubspec automatically

Safety

  • Check for pre-existing edits before touching release files and leave them intact.
  • Avoid broad dependency updates when a targeted version or configuration fix is sufficient.
  • Never claim a release succeeded based only on a successful build; distinguish build, upload, and rollout states.

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.

Check your setup, free