移动发布流水线

本条目介绍 移动发布流水线 的公开用途。DeepSkill 当前公开目录说明:“搭建移动端发布流水线 — Fastlane、代码签名、持续集成、Beta 分发、版本管理。当被问及“应用商店配置”、“发布流水线”、“Fastlane”、“Beta 分发”或“签名”时使用。” 适用场景包括部署发布与上云。本页根据公开目录资料和固定版本的上游仓库整理,建议使用前核对该版本的环境、工具、权限及数据处理要求。Skillπ 提供站方用途介绍与原站链接;原始 SKILL.md 和附件仅在对应许可允许时开放。

仓库
jeremylongshore/tons-of-skills-marketplace

安装方式

先用 Prompt 核对来源,也可切换到安装命令或下载可用的安装包。

安装方式

用 AI 助手安装

复制提示词,让助手先核对固定版本和依赖。

查看 Prompt收起 Prompt
先检查当前 Agent 是否已安装 SkillPI Skill Finder。如果尚未安装,请按官方仓库的说明安装并启用:https://github.com/Findskills/skillpi。然后使用 Skill Finder 打开此 SkillPI 详情页并定位 "touch-release":https://skillpi.com/zh/skills/deepskill-c92d30a2fa434c0eda0c805aaf63d7af1c7085daf8db9b10961548b1831080cc。安装前核对上游来源和版本:https://github.com/jeremylongshore/tons-of-skills-marketplace/blob/6ea46b08dce892944db7c16f28d0b5308d402402/plugins/ai-agency/tonone/skills/touch-release/SKILL.md。来源不一致时停止并说明差异。核对通过后,用 Skill Finder 安装目标 Skill,并报告安装路径和来源版本。

此命令从 GitHub 来源仓库获取指定技能。运行前请先查看源文件。

运行工具
npx skills add https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/6ea46b08dce892944db7c16f28d0b5308d402402/plugins/ai-agency/tonone/skills/touch-release --skill touch-release
许可协议: —

来源与配置

查看 GitHub 源码

jeremylongshore/tons-of-skills-marketplace固定提交 6ea46b08dce892944db7c16f28d0b5308d402402

配置方式待核实

请查看原始来源中的适用工具、依赖和权限要求。

安装实测待补充

本条目介绍 移动发布流水线 的公开用途。DeepSkill 当前公开目录说明:“搭建移动端发布流水线 — Fastlane、代码签名、持续集成、Beta 分发、版本管理。当被问及“应用商店配置”、“发布流水线”、“Fastlane”、“Beta 分发”或“签名”时使用。” 适用场景包括部署发布与上云。本页根据公开目录资料和固定版本的上游仓库整理,建议使用前核对该版本的环境、工具、权限及数据处理要求。Skillπ 提供站方用途介绍与原站链接;原始 SKILL.md 和附件仅在对应许可允许时开放。

↓ 0 下载 ↗ 0 分享点击

文件浏览

在原站浏览文件 ↗

原始 SKILL.md

打开原文 ↗
---
name: touch-release
description: Set up mobile release pipeline — Fastlane, code signing, CI, beta distribution, versioning. Use when asked about "app store setup", "release pipeline", "fastlane", "beta distribution", or "signing".
allowed-tools: Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
version: 0.6.4
author: tonone-ai <hello@tonone.ai>
license: MIT
---

# Set Up Mobile Release Pipeline

You are Touch — the mobile engineer on the Engineering Team.

## Steps

### Step 0: Detect Environment

Scan the project to understand the mobile platform and existing CI/CD:

```bash
# Platform detection
ls -la *.xcodeproj *.xcworkspace 2>/dev/null
ls -la android/ build.gradle* 2>/dev/null
cat package.json 2>/dev/null | grep -iE "react-native|expo"
cat pubspec.yaml 2>/dev/null

# Existing CI/CD
ls -la fastlane/ 2>/dev/null
cat fastlane/Fastfile 2>/dev/null | head -40
ls -la .github/workflows/ 2>/dev/null
cat bitrise.yml 2>/dev/null | head -20
ls -la .circleci/ 2>/dev/null

# Code signing
ls -la *.mobileprovision 2>/dev/null
ls -la fastlane/Matchfile 2>/dev/null
grep -r "signingConfig\|keystore\|KEYSTORE" --include="*.gradle" --include="*.gradle.kts" . 2>/dev/null | head -5

# Current version
grep -r "CFBundleShortVersionString\|versionName\|version\":" --include="*.plist" --include="*.gradle" --include="*.gradle.kts" --include="package.json" --include="pubspec.yaml" . 2>/dev/null | head -5
```

Note the platform, any existing Fastlane setup, CI provider, and code signing state.

### Step 1: Fastlane Setup

Create or update Fastlane configuration:

**Fastfile lanes:**

- **`beta`** — build and distribute to testers
  - Increment build number
  - Build the app (release configuration)
  - Upload to TestFlight (iOS) or Firebase App Distribution (Android)
  - Post to Slack/notification channel

- **`release`** — build and submit to app store
  - Increment version number (semantic versioning)
  - Build the app (release configuration)
  - Upload to App Store Connect (iOS) or Google Play Console (Android)
  - Create git tag
  - Post release notes

- **`test`** — run test suite
  - Run unit tests
  - Run UI tests (if applicable)
  - Generate coverage report

**Supporting files:**

```
fastlane/
  Fastfile        — lane definitions
  Appfile         — app identifier, team ID
  Matchfile       — code signing config (iOS)
  Pluginfile      — Fastlane plugins
  .env.default    — shared environment variables
  .env.beta       — beta-specific config
  .env.production — production-specific config
```

### Step 2: Code Signing

Set up code signing properly:

**iOS (using Match):**

- Configure `fastlane match` for certificate and provisioning profile management
- Set up a private git repo or cloud storage for certificates
- Generate profiles for: development, ad-hoc (beta), app-store (production)
- Document the match passphrase storage (do not commit it)

**Android:**

- Create or locate the release keystore
- Store keystore password securely (not in the repo)
- Configure signing in `build.gradle`
- Set up Play App Signing (let Google manage the release key)

### Step 3: App Store Metadata Structure

Set up metadata management:

```
fastlane/metadata/
  [locale]/
    name.txt            — app name
    subtitle.txt        — short description
    description.txt     — full description
    keywords.txt        — search keywords (iOS)
    release_notes.txt   — what's new
    privacy_url.txt     — privacy policy URL
  screenshots/
    [device]/           — organized by device type
```

- Use `fastlane deliver` (iOS) or `fastlane supply` (Android) for metadata sync
- Screenshots organized by device type and locale
- Privacy policy URL and support URL configured

### Step 4: CI Integration

Set up CI to build, test, and deploy:

**GitHub Actions example:**

- **On every PR:** run tests, lint, build (debug)
- **On merge to main:** run tests, build beta, deploy to testers
- **On tag/release:** build production, submit to store

CI configuration includes:

- Caching (CocoaPods, Gradle, node_modules, pub cache)
- Secrets management (signing keys, API keys, match passphrase)
- macOS runner for iOS builds
- Artifact upload (build logs, test results, IPA/APK)

### Step 5: Beta Distribution

Set up beta testing distribution:

**iOS:**

- TestFlight via `fastlane pilot`
- Internal testers (team) — immediate distribution
- External testers — requires brief review (~24h)

**Android:**

- Firebase App Distribution via `fastlane firebase_app_distribution`
- Or Google Play Internal Testing track
- Tester groups configured

**Both:**

- Tester group management
- Build notes auto-generated from commits
- Notification to testers on new build

### Step 6: Version Bumping

Automate version management:

- **Version number:** semantic versioning (major.minor.patch)
- **Build number:** auto-incrementing (CI build number or timestamp)
- **Bump script:** `fastlane bump_patch`, `bump_minor`, `bump_major`
- **Single source of truth** — version defined in one place, not scattered across files
- **Git tag on release** — tag format: `v1.2.3`

### Step 7: Changelog Generation

Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.

Automate changelog from git history:

- Generate from conventional commits or PR titles since last tag
- Format for app store release notes (character limits: 4000 for iOS, 500 for Play Store)
- Include in build metadata
- Store in `CHANGELOG.md` for the team

Present a summary:

```
## Release Pipeline Configured

**Platform:** [iOS/Android/Both]

### Lanes
- `fastlane beta` — build + TestFlight/Firebase App Distribution
- `fastlane release` — build + App Store/Play Store submission
- `fastlane test` — test suite

### Code Signing
- iOS: [match/manual] — profiles in [location]
- Android: [keystore location] — Play App Signing [enabled/disabled]

### CI
- Provider: [GitHub Actions/Bitrise/etc]
- PR: test + build
- Main: test + beta deploy
- Tag: production release

### Files Created
[List key files]

### Next Steps
- [ ] Add signing credentials to CI secrets
- [ ] Configure tester groups
- [ ] First beta build: `fastlane beta`
```

## Delivery

If output exceeds the 40-line CLI budget, invoke `/atlas-report` with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.

当前收录版本

0.6.4

核对来源版本 ↗

质量评测

满分 100。前四项来自 DeepSkill 收录的质量报告。

场景价值95/100
评分依据

提供完整的移动端发布流水线搭建方案,涵盖 Fastlane、代码签名、CI/CD、Beta 分发等核心功能

触发精准92/100
评分依据

触发词覆盖全面且精准,包括应用商店配置、发布流水线、Fastlane、Beta 分发、签名等关键场景

结构规范90/100
评分依据

结构清晰,分步骤详细说明,包含环境检测、配置、集成等完整流程

执行可靠85/100
评分依据

工具来源明确,参数配置合理,覆盖主要异常场景

证据可验 (前四项均值)91/100
计算方式

取前四项原始分值的算术平均,四舍五入取整。可通过收录报告核对各项评分与说明,运行记录需单独查证。

权限与使用前检查

根据当前主文档自动整理,命中内容可能是示例或防护说明;不是实际权限声明,也未覆盖附件、外部依赖或运行行为。

  • 账号、密钥或授权

    使用专用、最小权限账号,不把密钥粘贴到公开内容或命令日志;核对接收数据的服务与租户。

    主文档提及 · 第 207 行

本站展示提示不会授予权限。涉及文件改动、密钥、外部发送或费用时,仍由你使用的工具按需确认。

安全评级与访问范围

risk · 静态证据核验,不代表运行安全保证。

使用前请由宿主核对并授权实际文件读写、外部服务和联网目的地;本站的核验不会授予任何运行权限。

来源与使用声明 SkillPi 的部分技能资料来自公开来源或创作者提交。第三方内容的权利归各自权利人所有。安装或运行前,请查看原站的许可、权限要求和使用风险。

来源与使用

请按详情页的作者、原始来源和许可证核对使用条件,运行前检查技能需要的权限。目录收录不等于已验证安装或安全性。