agentleFS
Sign inStart free
SUDARSHANCHAUDHARISUDARSHANCHAUDHARI/DroidForge/skills/release-workflow/SKILL.md

release-workflow

Skill1 starsChanged 9 days agoMITView on GitHub

End-to-end Android app release workflow for solo developers — pre-release steps, build commands, ADB install testing, Play Console submission, post-release git tagging, and staged rollout strategy.

  • Commits and pushes

3 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions3 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 3

    1. fxstein/ai-todo★ 16same name
    2. crux-cli/crux★ 0same name
    3. sametbrr/github-manager★ 0same 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.

The file

We split this skill into the rules it gives an agent

9 rules. 0 are common, 7 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 7

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Write release notes for this version (what changed for users, not internal details)

    line 12
  2. Very specific:

    Verify isMinifyEnabled = true and isShrinkResources = true in release buildType

    line 13
  3. Distinctive:

    Verify the AAB is signed with the release key (not debug):

    line 18
  4. Distinctive:

    Run through all core user flows

    line 34
  5. Distinctive:

    Test on a device running the minimum supported Android version

    line 36
  6. Distinctive:

    Verify in-app purchases / ads work in release mode (sandbox for IAP)

    line 37
  7. Distinctive:

    Update app tracker with: release date, new version, Play review status.

    line 58
  8. Distinctive:

    Never release to 100% immediately for production apps:

    line 67
  9. Very specific:

    Run /droidforge:release-checklist before every submission.

    line 94

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “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

Solo Developer Android Release Workflow

Step 1 — Pre-release

  1. Bump versionCode (+1 always) and versionName (semver) using /droidforge:version-bump
  2. Write release notes for this version (what changed for users, not internal details)
  3. Verify isMinifyEnabled = true and isShrinkResources = true in release buildType
  4. Run clean build:
    ./gradlew clean bundleRelease
  5. Verify the AAB is signed with the release key (not debug):
    ./gradlew signingReport

Step 2 — Test before submitting

# Build a release APK for local testing
./gradlew assembleRelease

# Install on connected device
adb install -r app/build/outputs/apk/release/app-release.apk

Testing checklist:

  • Run through all core user flows
  • Confirm no debug toasts, logs, or test features visible
  • Test on a device running the minimum supported Android version
  • Verify in-app purchases / ads work in release mode (sandbox for IAP)

Step 3 — Play Console submission

  1. Open Play Console → [App] → Release → Production
  2. Create new release
  3. Upload the AAB from app/build/outputs/bundle/release/app-release.aab
  4. Paste release notes (use the same text you prepared in Step 1)
  5. Resolve any policy warnings (yellow/red banners)
  6. Review and submit

Step 4 — Post-release

# Create annotated tag (show to user, confirm before running)
git tag -a v[versionName] -m "Release [versionName] — [brief description]"

# Push tag
git push origin v[versionName]

Update app tracker with: release date, new version, Play review status.

Monitor Play Console for 24–48 hours after rollout:

  • Crash-free rate (target: > 99%)
  • ANR rate (target: < 0.47% — Google's policy threshold)
  • User reviews mentioning crashes

Staged rollout strategy

Never release to 100% immediately for production apps:

StageRollout %Wait
110–20%24h
250%24h
3100%—

Halt rollout and investigate if:

  • Crash-free rate drops below 99%
  • ANR rate exceeds 0.47%
  • Sudden spike in 1-star reviews

To halt: Play Console → [App] → Release → Production → Halt rollout

Build output locations

OutputPath
Release AABapp/build/outputs/bundle/release/app-release.aab
Release APKapp/build/outputs/apk/release/app-release.apk
Mapping fileapp/build/outputs/mapping/release/mapping.txt

Upload mapping.txt to Play Console for deobfuscated crash reports.

Play Store submission checklist

Run /droidforge:release-checklist before every submission. Key items:

  • versionCode > last published version
  • Release signing config confirmed (not debug)
  • Privacy policy URL live and correct
  • Store listing current (screenshots show current UI)
  • Data safety section accurate

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