Mobile CI/CD Evolution

Overview

Read current pipeline configuration, identify bottlenecks and risk points, and propose safe incremental CI/CD improvements.

Workflow

1. Snapshot current CI/CD

• Run scripts/ci_cd_snapshot.sh <repo_root> first.
• Gather pipeline files, release automation files, and mobile module signals.

2. Baseline reliability and speed risks

• Detect missing cache usage, oversized single jobs, and release-critical single points of failure.
• Detect missing test/lint gates or unclear release approval steps.

3. Propose safe incremental improvements

• Prioritize low-risk wins first (cache correctness, split long jobs, deterministic test steps, artifact clarity).
• Keep each recommendation reversible and scoped.
• Avoid full pipeline rewrites unless explicitly requested.

4. Protect release flow

• Ensure release jobs have clear gate criteria and rollback notes.
• Keep publish paths (Fastlane/store steps) explicit and auditable.

5. Publish roadmap

• Provide Now, Next, and Later actions with risk and expected benefit.
• Include exact files and minimal patch scope.

Output Format

Use this structure:

# CI/CD Improvement Report

## Current State
- Pipelines detected:
- Release automation detected:
- Key risks:

## Safe Improvements (Now)
1. [change] - expected benefit - risk

## Next Improvements
1. [change] - expected benefit - risk

## Later Improvements
1. [change] - expected benefit - risk

## Patch Scope
- Files to edit:
- Rollback plan:

## Verification
- Commands/checks:
- Success criteria:

Guardrails

• No CI/CD platform migration by default.
• No release flow breaking changes without explicit approval.
• Default to smallest safe change set.
• If confidence is low, recommend NO-CHANGE and ask for missing evidence.

Resources

• scripts/ci_cd_snapshot.sh
• references/ci-cd-improvement-checklist.md
• references/mobile-pipeline-patterns.md