mobile-release
Skill37 starsChanged 36 days agoMITView on GitHub
Use when preparing a mobile app for release. Covers versioning, signing, staged rollout, crash monitoring, store review requirements, and rollback when an update goes wrong. Trigger on "ready to submit to the app store", "app got rejected in review", "crash rate spiked after the update", "set up a staged rollout". Do not use for general CI pipeline design — see the ci-cd skill.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- avelikiy/great_ctotheir own version, first seen Nov 15, 2026
- wrsilva/reis-mobiletheir own version, first seen Nov 8, 2026
- SWEStash/swe-workflow-skillstheir own version, first seen Nov 8, 2026
- Kushpawan/kmp-mobile-skillstheir own version, first seen Nov 1, 2026
- RSSNext/Folotheir own version, first seen Oct 8, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- RSSNext/Folo★ 39ksame name
- avelikiy/great_cto★ 115same name
- Kushpawan/kmp-mobile-skills★ 15same name
- wrsilva/reis-mobile★ 8same name
- SWEStash/swe-workflow-skills★ 1same 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 repository137 other files it gives its agents.
- agent-instructionsSkill
- agent-memorySkill
- hooksSkill
- plugin-developmentSkill
- skill-authoringSkill
- skill-reviewSkill
- slash-commandsSkill
- subagentsSkill
- agent-designSkill
- context-engineeringSkill
- fine-tuningSkill
- llm-cost-optimizationSkill
- llm-evaluationSkill
- llm-integrationSkill
- mcp-serverSkill
- ml-pipelineSkill
- model-selectionSkill
- prompt-engineeringSkill
- ragSkill
- structured-outputSkill
- api-designSkill
- background-jobsSkill
- cachingSkill
- djangoSkill
- event-driven-architectureSkill
- fastapiSkill
- graphqlSkill
- microservicesSkill
- nestjsSkill
- realtime-websocketsSkill
- spring-bootSkill
- competitive-analysisSkill
- lead-researchSkill
- product-analysisSkill
- resumeSkill
- user-researchSkill
- database-performanceSkill
- data-modelingSkill
- data-qualitySkill
- pandasSkill
- postgresSkill
- sparkSkill
- brand-guidelinesSkill
- generative-artSkill
- themingSkill
- ui-reviewSkill
- visual-designSkill
- architecture-decisionsSkill
- bug-fix-protocolSkill
- cli-developmentSkill
- code-reviewSkill
- debuggingSkill
- design-patternsSkill
- domain-modelingSkill
- git-workflowSkill
- legacy-modernizationSkill
- refactoringSkill
- repository-explorationSkill
- simple-designSkill
- system-designSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 55
Every release needs a kill switch for its risky feature.
- Distinctive: line 58
Never bump only the marketing version.
- Distinctive: line 98
Keep the previous implementation in the binary for one release cycle after replacing it.
“Common” is measured: kept by at least 6 in 10 of the 5 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.
Files
Mobile Release
Purpose
Ship a mobile release safely. Unlike a web deploy, a bad mobile release cannot be rolled back — users have already installed it. The process must therefore prevent the bad release rather than recover from it.
When to Use
- Preparing a store submission.
- Setting up a mobile CI/CD pipeline.
- Responding to a crash spike after a release.
- Establishing a release process for a team that does not have one.
Capabilities
- Version and build-number strategy.
- Code signing and credential management.
- Staged rollout and kill switches.
- Crash and performance monitoring with alerting.
- Store review preparation and common rejection avoidance.
Inputs
- The build, its version, and what changed.
- Store credentials and signing keys.
- The current crash-free rate as a baseline.
Outputs
- A signed, reproducible build from CI.
- A staged rollout plan with defined abort criteria.
- Monitoring that will detect a regression before users report it.
Workflow
- Build in CI, never on a laptop — A build that only one machine can produce is a build you cannot reproduce when it breaks.
- Test the release build — On real devices, including the oldest supported OS version. Debug builds hide crashes that only occur under release optimization.
- Ship behind a flag — Anything risky is remotely toggleable. A feature flag is the only rollback a mobile app has.
- Stage the rollout — 1%, then 10%, then 50%, then 100%, with at least a day between steps. Watch the crash-free rate at each stage.
- Define the abort criteria before you start — For example: crash-free sessions below 99.5%, or any new crash affecting more than 0.1% of sessions. Halt the rollout automatically, do not debate it.
- Keep the previous build ready — On Android you can halt a staged rollout; on iOS you can only submit a new build. Have one prepared.
Best Practices
- A staged rollout is the only safety net that exists. Shipping to 100% immediately is a decision to have no rollback.
- Every release needs a kill switch for its risky feature. Server-side flags cost a day to build and save a release.
- Monitor the crash-free session rate, not the crash-free user rate. The latter hides a crash that occurs on one screen in ten sessions.
- Symbolicate crash reports in CI by uploading dSYMs and mapping files as part of the build. A crash report without symbols is useless at 2am.
- Never bump only the marketing version. The build number must increase on every submission or the store rejects it.
- Store review rejections cluster around permissions, in-app purchase rules, and misleading metadata. Read the guideline before you build the feature, not after the rejection.
Examples
Rollout gate with explicit abort criteria:
# .github/workflows/release.yml (excerpt)
- name: Staged rollout to Play Store
run: |
fastlane supply \
--track production \
--rollout 0.01 \
--aab app/build/outputs/bundle/release/app-release.aab
- name: Guard the rollout
run: |
# 6 hours of soak, then check the crash-free session rate before proceeding.
sleep 21600
RATE=$(crashlytics-cli crash-free-rate --version "$VERSION" --window 6h)
echo "crash-free sessions: ${RATE}%"
if (( $(echo "$RATE < 99.5" | bc -l) )); then
fastlane supply --track production --rollout 0 --skip-upload-aab # halt
echo "::error::Rollout halted: crash-free rate ${RATE}% is below the 99.5% threshold"
exit 1
fiA kill switch that makes the release recoverable:
if (await flags.isEnabled('checkout.new_payment_sheet')) {
return NewPaymentSheet();
}
return LegacyPaymentSheet(); // the fallback path stays in the binary for one releaseNotes
- Keep the previous implementation in the binary for one release cycle after replacing it. A flag that flips to code that is not there is not a kill switch.
- Apple's expedited review exists and works, but it is a limited resource — use it for a genuine crash-level regression, not for a missed marketing date.
- Android's in-app update API can force users off a broken version. iOS has no equivalent, which is why a server-side flag matters more there.
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
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.

