AGENT SKILL

prepare-release

Creates a release branch (release/vX.Y.Z) from main, verifies the app's MARKETING_VERSION already matches before branching, pushes the branch and leaves it open for QA, and optionally hands off to the create-ipa skill to export a production-scheme build. Use when a developer is ready to cut a new release branch.

License 许可
MIT
最近更新
2026-08-21
Stars
★ 0
Forks
0

01 前言 Front Matter

name
prepare-release
license
MIT
metadata
{ "author": "ICT", "version": "1.0" }
description
Creates a release branch (release/vX.Y.Z) from main, verifies the app's MARKETING_VERSION already matches before branching, pushes the branch and leaves it open for QA, and optionally hands off to the create-ipa skill to export a production-scheme build. Use when a developer is ready to cut a new release branch.
argument-hint
[version]

02 资源文件 2

03 SKILL.md 正文

ICT iOS Team — This skill cuts release branches following ICT's release process. All output must adhere exactly to the pattern defined in references/branch-and-version.md. Do not deviate.

🚀 [CLAUDE] Release Workflow → Prepare Release Branch

You are a Senior iOS Engineer on the ICT team, acting as the developer's release assistant. Your job is to cut a release branch for QA, catching a version mismatch before it happens, and optionally hand off to the create-ipa skill for a build — without merging anything, tagging anything, or touching project.pbxproj.

Follow this process, in order. Do not skip steps or reorder them.


1. Get the version

If the developer already passed a version as an argument, use it. Otherwise ask for the version to release, in X.Y.Z form (e.g. 1.1.7). Validate against ^\d+\.\d+\.\d+$ — reject and re-ask if it doesn't match, don't guess at what they meant.

2. Pre-flight checks

Follow references/branch-and-version.md:

  1. git fetch origin, confirm local main is up to date with origin/main (fast-forward pull if needed — never branch from a stale main).
  2. Confirm release/v<version> doesn't already exist locally or on origin. If it does, stop and tell the developer.

3. Verify the version — never edit it

Follow the "Version verification" section of references/branch-and-version.md: locate the main app target's MARKETING_VERSION in project.pbxproj and compare it to the version from step 1.

  • Matches → continue to step 4.
  • Doesn't match → stop here. Report the current value (with file/line), the requested version, and that the developer needs to bump MARKETING_VERSION on main first. Do not create the branch, and do not edit project.pbxproj yourself under any circumstances.

4. Create and push the branch

  1. Confirm the exact branch name (release/v<version>) with the developer before creating it.
  2. git checkout -b release/v<version> from main.
  3. Confirm before pushing — pushing is visible to the rest of the team. Then git push -u origin release/v<version>.
  4. Tell the developer the branch is pushed and intentionally left open: no PR, no merge, no tag — that's outside this skill's scope.

5. Offer to hand off to create-ipa

Ask whether the developer wants a .ipa prepared now. If no, stop here and report the branch as done.

If yes: invoke the create-ipa skill (do not reimplement its steps here). At this phase it's usually the production/main scheme that's wanted — since a release branch is typically cut ahead of an App Store submission — but let the developer pick any scheme create-ipa offers, same as if they'd invoked it standalone. Pass along the version from step 1 as the suggested label, and note the branch just created (release/v<version>) as what's currently checked out.

6. Final summary

Report back: branch name, push status, and (if create-ipa was invoked) whatever it reports for the .ipa path(s).


Core Instructions

  • Never edit project.pbxproj. This skill verifies the version; it does not bump it. A mismatch is a stop condition, not something to fix inline.
  • Never create a git tag. Not part of this workflow.
  • Never open a pull request or merge the release branch. It's left open on purpose for QA.
  • Never push to origin without explicit confirmation — it's visible to the rest of the team.
  • IPA export is not this skill's job — delegate to create-ipa rather than duplicating its archive/export/signing steps here.

References

  • references/branch-and-version.md — branch naming (release/vX.Y.Z), pre-flight checks, and the version-verification procedure.
  • The create-ipa skill — invoked optionally in step 5 for the actual .ipa build.

04 同仓库更多 Skills

ictech-projects
ictech-projects/ios-claude-skills

unit-testing

Writes or reviews iOS unit tests for data layer (Repository) and ViewModel code, following ICT's XCTest + Combine testing patterns.

★ 0
ictech-projects
ictech-projects/ios-claude-skills

unit-testing

Writes or reviews iOS unit tests for data layer (Repository) and ViewModel code, supporting both XCTest and Swift Testing frameworks. Use when adding new unit tests, reviewing existing tests for compliance, or expanding test coverage for a domain.

★ 0
ictech-projects
ictech-projects/ios-claude-skills

swiftui-reviewer

Comprehensively reviews SwiftUI code for best practices on modern APIs, maintainability, and performance. Use when reading, writing, or reviewing SwiftUI projects.

★ 0
ictech-projects
ictech-projects/ios-claude-skills

swiftui-reviewer

Comprehensively reviews SwiftUI code for best practices on modern APIs, maintainability, and performance. Use when reading, writing, or reviewing SwiftUI projects.

★ 0
ictech-projects
ictech-projects/ios-claude-skills

security-review

Comprehensive iOS security assessment for the ICT iOS team. Reviews authentication, data storage, network security, secrets management, and more against OWASP MASVS and Apple security guidelines. Use when auditing or reviewing iOS app security.

★ 0
ictech-projects
ictech-projects/ios-claude-skills

security-review

Comprehensive iOS security assessment for the ICT iOS team. Reviews authentication, data storage, network security, secrets management, and more against OWASP MASVS and Apple security guidelines. Use when auditing or reviewing iOS app security.

★ 0