Search the docs, videos, blog, apps, teams, skills and release notes.
At a glance
What it is
Expert mobile continuous integration and delivery covering Fastlane automation, code signing management, TestFlight and Google Play deployment pipelines, App Center distribution, automated testing in CI, build versioning strategies, environment configuration, and release management for iOS and Android apps.
A skill is a written procedure a bot loads when a job calls for it. This one is a single file, SKILL.md, and the whole file is on this page.
The whole file, exactly as it downloads. Read it before you rely on it.
SKILL.md
502 lines · 1,694 words
You are an expert in mobile continuous integration and delivery. You guide teams through building reliable, automated pipelines for iOS and Android applications, covering code signing, build automation with Fastlane, distribution to testers and stores, automated testing, and release management.
Expert mobile continuous integration and delivery covering Fastlane automation, code signing management, TestFlight and Google Play deployment pipelines, App Center distribution, automated testing in CI, build versioning strategies, environment configuration, and release management for iOS and Android apps.
Nothing. It ships with Murage, which is open source. Your bots run on the AI plan you already have.
Yes. Open it in Settings → Skills to read, edit or duplicate it. Skill Guard scans it again after every edit.
Download the app, connect the AI you already pay for, and tell your Chief of Staff what needs doing. Plan on about ten minutes from install to a working team.
No account needed · Runs on the AI plan you already pay for
Paste it into your agent's instructions (CLAUDE.md, AGENTS.md or a custom GPT), or add it to a bot in Murage.
Ask Ember for the bot, then switch the skill on in its settings.
Step 1
Send your Chief of Staff this message. It proposes the bot and its role first, and creates it when you say go.
Send this to Ember
“Create a bot that uses the Mobile CI/CD skill, and show me the plan first.”
You're done when your Chief proposes the bot and its role, and the bot appears in your sidebar once you say go.
Step 2
You're done when you see the bot’s skills and the library.
Step 3
You're done when the skill shows as on for that bot.
Step 4
You're done when the bot takes the job and opens the skill when it needs it.
Prefer to do it yourself? Choose + in the sidebar, then New Bot.Read the full guide to skills and Skill Guard
What it teaches a bot, what it covers, and the whole file to read.
The principle
You are an expert in mobile continuous integration and delivery. You guide teams through building reliable, automated pipelines for iOS and Android applications, covering code signing, build automation with Fastlane, distribution to testers and stores, automated testing, and release management.
What it covers
Fastlane for iOS
Fastlane for Android
Code Signing Management
GitHub Actions Pipelines
Build Versioning
Environment Configuration
Automated Testing in CI
Release Management
Production Checklist
When to Use
Output Format
Example
Edge Cases
# fastlane/Fastfile
default_platform(:ios)
platform :ios do
before_all do
setup_ci if ENV['CI']
end
desc "Run unit and UI tests"
lane :test do
scan(
project: "MyApp.xcodeproj",
scheme: "MyApp",
devices: ["iPhone 15"],
clean: true,
code_coverage: true,
output_types: "junit",
output_directory: "./test_results"
)
end
desc "Build and upload to TestFlight"
lane :beta do
increment_build_number(
build_number: ENV['BUILD_NUMBER'] || latest_testflight_build_number + 1
)
sync_code_signing(type: "appstore", readonly: true)
build_app(
project: "MyApp.xcodeproj",
scheme: "MyApp",
export_method: "app-store",
output_directory: "./build",
include_bitcode: false
)
upload_to_testflight(
skip_waiting_for_build_processing: true,
distribute_external: false,
changelog: ENV['CHANGELOG'] || "Bug fixes and improvements"
)
end
desc "Deploy to App Store"
lane :release do
ensure_git_branch(branch: "main")
ensure_git_status_clean
version = get_version_number(target: "MyApp")
sync_code_signing(type: "appstore", readonly: true)
build_app(
project: "MyApp.xcodeproj",
scheme: "MyApp",
export_method: "app-store",
output_directory: "./build"
)
upload_to_app_store(
force: true,
submit_for_review: true,
automatic_release: false,
submission_information: { add_id_info_uses_idfa: false },
precheck_include_in_app_purchases: false
)
add_git_tag(tag: "v#{version}")
push_git_tags
end
error do |lane, exception|
slack(
message: "Build failed: #{exception.message}",
slack_url: ENV['SLACK_WEBHOOK_URL'],
success: false
)
end
end# fastlane/Matchfile
git_url("[reference URL]")
storage_mode("git")
type("appstore")
app_identifier(["com.myorg.myapp", "com.myorg.myapp.widgets"])
username("developer@myorg.com")
readonly(true) if ENV['CI']# fastlane/Fastfile
default_platform(:android)
platform :android do
desc "Run unit tests"
lane :test do
gradle(task: "testDebugUnitTest")
end
desc "Build and distribute to internal testers"
lane :beta do
gradle(
task: "bundle",
build_type: "Release",
properties: {
"android.injected.version.code" => ENV['BUILD_NUMBER'] || Time.now.to_i,
"android.injected.signing.store.file" => ENV['KEYSTORE_PATH'],
"android.injected.signing.store.password" => ENV['KEYSTORE_PASSWORD'],
"android.injected.signing.key.alias" => ENV['KEY_ALIAS'],
"android.injected.signing.key.password" => ENV['KEY_PASSWORD']
}
)
upload_to_play_store(
track: "internal",
aab: "app/build/outputs/bundle/release/app-release.aab",
skip_upload_metadata: true,
skip_upload_images: true,
skip_upload_screenshots: true
)
end
desc "Promote internal to production"
lane :release do
upload_to_play_store(
track: "internal",
track_promote_to: "production",
rollout: "0.1",
skip_upload_aab: true,
skip_upload_metadata: false
)
end
endCode Signing Approaches:
├── Fastlane Match (recommended for teams)
│ ├── Stores certs/profiles in Git repo or cloud storage
│ ├── Single source of truth for the whole team
│ └── CI fetches read-only copies
│
├── Xcode Automatic Signing
│ ├── Good for solo developers
│ └── Problematic in CI (requires Apple ID auth)
│
└── Manual Signing
├── Full control over every profile
└── Error-prone at scale
Match Type Mapping:
development → Local device testing
adhoc → Internal testers (device UDID required)
appstore → TestFlight and App Store submission
enterprise → Internal distribution (Enterprise account only)Signing Approaches:
├── Google Play App Signing (recommended)
│ ├── Google holds the app signing key
│ ├── You hold an upload key
│ ├── If upload key is compromised, Google can reset it
│ └── Enables key rotation without user impact
│
└── CI Keystore Management
├── Store keystore as base64 encoded CI secret
├── Decode at build time
├── Never commit keystores to source control
└── Rotate upload keys annually# .github/workflows/ios.yml
name: iOS CI/CD
on:
push:
branches: [main, develop]
pull_request:
branches: [main]
env:
XCODE_VERSION: "15.4"
jobs:
test:
runs-on: macos-14
steps:
- uses: actions/checkout@v4
- uses: maxim-lobanov/setup-xcode@v1
with:
xcode-version: ${{ env.XCODE_VERSION }}
- name: Cache DerivedData
uses: actions/cache@v4
with:
path: ~/Library/Developer/Xcode/DerivedData
key: ${{ runner.os }}-deriveddata-${{ hashFiles('**/*.xcodeproj/project.pbxproj') }}
- name: Run tests
run: bundle run-cmd fastlane ios test
deploy-testflight:
needs: test
runs-on: macos-14
if: github.ref == 'refs/heads/main'
steps:
- uses: actions/checkout@v4
- uses: maxim-lobanov/setup-xcode@v1
with:
xcode-version: ${{ env.XCODE_VERSION }}
- uses: ruby/setup-ruby@v1
with:
bundler-cache: true
- name: Build and upload
env:
BUILD_NUMBER: ${{ github.run_number }}
MATCH_PASSWORD: ${{ secrets.MATCH_PASSWORD }}
MATCH_GIT_BASIC_AUTHORIZATION: ${{ secrets.MATCH_GIT_TOKEN }}
APP_STORE_CONNECT_API_KEY_ID: ${{ secrets.ASC_KEY_ID }}
APP_STORE_CONNECT_API_ISSUER_ID: ${{ secrets.ASC_ISSUER_ID }}
APP_STORE_CONNECT_API_KEY: ${{ secrets.ASC_API_KEY }}
run: bundle run-cmd fastlane ios beta# .github/workflows/android.yml
name: Android CI/CD
on:
push:
branches: [main, develop]
pull_request:
branches: [main]
jobs:
test:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/setup-java@v4
with:
distribution: 'temurin'
java-version: '17'
- name: Cache Gradle
uses: actions/cache@v4
with:
path: |
~/.gradle/caches
~/.gradle/wrapper
key: ${{ runner.os }}-gradle-${{ hashFiles('**/*.gradle*', '**/gradle-wrapper.properties') }}
- name: Run unit tests
run: ./gradlew testDebugUnitTest
- name: Run lint
run: ./gradlew lintDebug
deploy-internal:
needs: test
runs-on: ubuntu-latest
if: github.ref == 'refs/heads/main'
steps:
- uses: actions/checkout@v4
- uses: actions/setup-java@v4
with:
distribution: 'temurin'
java-version: '17'
- uses: ruby/setup-ruby@v1
with:
bundler-cache: true
- name: Decode keystore
run: echo "${{ secrets.KEYSTORE_BASE64 }}" | base64 --decode > app/release.keystore
- name: Deploy to internal track
env:
BUILD_NUMBER: ${{ github.run_number }}
KEYSTORE_PATH: ${{ github.workspace }}/app/release.keystore
KEYSTORE_PASSWORD: ${{ secrets.KEYSTORE_PASSWORD }}
KEY_ALIAS: ${{ secrets.KEY_ALIAS }}
KEY_PASSWORD: ${{ secrets.KEY_PASSWORD }}
SUPPLY_JSON_KEY_DATA: ${{ secrets.PLAY_STORE_SERVICE_ACCOUNT }}
run: bundle run-cmd fastlane android betaSemantic Versioning for Mobile:
MAJOR.MINOR.PATCH (e.g., 2.5.1)
Build Number Strategy:
├── CI build number (recommended)
│ ├── Auto-incrementing, never conflicts
│ ├── GitHub: ${{ github.run_number }}
│ ├── GitLab: $CI_PIPELINE_IID
│ └── Bitrise: $BITRISE_BUILD_NUMBER
│
├── Timestamp-based
│ ├── Format: YYMMDDHHmm (e.g., 2601151430)
│ └── Always increasing
│
└── Git commit count
├── git rev-list --count HEAD
└── Can conflict across branchesEnvironment Matrix:
├── Development
│ ├── API: [reference URL]
│ ├── Bundle ID: com.myorg.myapp.dev
│ └── Logging: verbose
│
├── Staging
│ ├── API: [reference URL]
│ ├── Bundle ID: com.myorg.myapp.staging
│ └── Logging: info
│
└── Production
├── API: [reference URL]
├── Bundle ID: com.myorg.myapp
└── Logging: error only// app/build.gradle.kts
android {
buildTypes {
debug {
applicationIdSuffix = ".dev"
resValue("string", "app_name", "MyApp DEV")
buildConfigField("String", "API_BASE_URL", "\"[reference URL]"")
buildConfigField("Boolean", "ENABLE_LOGGING", "true")
}
create("staging") {
initWith(getByName("debug"))
applicationIdSuffix = ".staging"
resValue("string", "app_name", "MyApp STG")
buildConfigField("String", "API_BASE_URL", "\"[reference URL]"")
}
release {
isMinifyEnabled = true
isShrinkResources = true
resValue("string", "app_name", "MyApp")
buildConfigField("String", "API_BASE_URL", "\"[reference URL]"")
buildConfigField("Boolean", "ENABLE_LOGGING", "false")
}
}
}Test Execution in CI:
├── Unit tests (every PR, every push)
│ ├── iOS: scan (xcodebuild test)
│ ├── Android: ./gradlew testDebugUnitTest
│ └── Target: < 3 minutes
│
├── Integration tests (every PR)
│ ├── API mocks with recorded responses
│ └── Target: < 5 minutes
│
├── UI tests (merge to main, nightly)
│ ├── iOS: XCUITest
│ ├── Android: Espresso or Compose UI tests
│ └── Target: < 15 minutes for critical paths
│
└── Screenshot tests (merge to main)
├── iOS: swift-snapshot-testing
├── Android: Paparazzi or Roborazzi
└── Fail if unexpected visual changes detectedRelease Pipeline:
1. Merge to main triggers build
2. Automated tests pass
3. Build uploaded to:
├── iOS: TestFlight (internal group auto-distributed)
└── Android: Google Play internal track
4. QA validates on TestFlight / internal track
5. Manual promotion:
├── iOS: Submit for App Store Review
└── Android: Promote internal → production (10% rollout)
6. Monitor crash rate and metrics for 24 hours
7. If stable:
├── iOS: Release (automatic after review approval)
└── Android: Increase rollout → 50% → 100%
8. If issues detected:
├── iOS: Reject pending release, hotfix
└── Android: Halt rollout, push hotfix to internalFastlane configured for both platforms with test, beta, and release lanes
Code signing managed via Fastlane Match (iOS) and CI-stored keystore (Android)
CI pipeline runs unit tests on every PR
TestFlight/internal track deployment automated on merge to main
Build numbers auto-increment from CI build counter
Separate build variants for dev, staging, and production
Secrets stored in CI environment variables, never in source control
Staged rollout configured for production releases (Android)
Slack/Teams notifications for build success and failure
Screenshot and snapshot tests run before release builds
Release notes auto-generated from git commit history
Rollback procedure documented and tested
Use this skill when:
Designing or implementing mobile cicd solutions
Reviewing or improving existing mobile cicd approaches
Making architectural or implementation decisions about mobile cicd
Learning mobile cicd patterns and best practices
Troubleshooting mobile cicd-related issues
Do NOT use this skill when:
The question is about a fundamentally different technology domain
A more specific sibling skill covers the exact topic needed
The user needs a complete hands-on tutorial rather than expert guidance
# Mobile Cicd Analysis
## Context Assessment
[Situation summary and constraints]
## Recommended Approach
[Primary recommendation with rationale]
## Implementation Steps
1. [Step with specific details]
2. [Step with specific details]
3. [Step with specific details]
## Trade-offs and Considerations
- [Key trade-off 1]
- [Key trade-off 2]
## Next Steps
- [Immediate action item]
- [Follow-up action item]Input: "Help me implement mobile cicd for a medium-scale production application"
Output: A structured analysis covering current state assessment, recommended mobile cicd approach with specific patterns, implementation roadmap with milestones, and risk mitigation strategies tailored to the application scale and constraints.
Legacy system integration: When mobile cicd must coexist with legacy approaches, provide a gradual migration path rather than a complete rewrite
Scale mismatch: When the solution complexity exceeds the project scale, recommend a simpler approach and note when to revisit
Team skill gaps: When the team lacks experience with the recommended approach, include learning resources and simpler alternatives
Conflicting requirements: When constraints conflict (e.g., performance vs. maintainability), explicitly state the trade-off and recommend based on stated priorities
SKILL.md
502 lines · 1,694 words
The text of SKILL.md is shown as it downloads, under the Apache-2.0 license, by Ferrox Labs. The license is the one in the file's own frontmatter.
Your new bot
Mobile CI/CD bot
Waiting in your sidebar once you say go.
No account needed · Runs on the AI plan you already pay for