xcode-archive-release
Xcode Archive & Release
Release an Apple app by bumping version/build metadata, archiving with Xcode, exporting and uploading to App Store Connect, then tagging the released HEAD in git.
Use when
- The user wants to archive and upload an iOS or macOS app to App Store Connect
- The user wants to release from an explicit version/build or infer them from a git tag
- The user needs to retry an upload without rebuilding unless necessary
Prerequisites
- macOS with Xcode and
xcodebuildavailable - A signed Xcode project with a valid scheme
- Access to the correct Apple Developer team and App Store Connect account
- A clean understanding of the target project, scheme, platform list, version, and build number
The main helper is scripts/xcode-release.sh. The bundled assets/ExportOptions-AppStore.plist sets method=app-store and destination=upload, so the default flow uploads directly to App Store Connect without a separate altool step. After a successful automatic upload, the script creates the annotated git tag v<version>-<build> on the current HEAD and pushes that exact tag to the branch's upstream remote, or origin if no upstream remote is configured.
More from grepug/skills
github-issue-workflow
Use when work should be tracked and executed through GitHub Issues instead of repo-local todo files. Helps agents adopt a repo's existing issue templates, labels, and project conventions when present, or fall back to a portable seed plus execution workflow when they are missing.
9plan-driven-change
Approval-gated, plan-first workflow for larger code changes. Use when the user asks to build a new capability or make a non-trivial change that touches multiple files, crosses module boundaries, or involves architectural decisions. Do NOT use for bug fixes, one-line tweaks, dependency bumps, or small config changes. The workflow is: clarify intent, get user approval, write a rich plan with interface stubs and checklist, get user approval again, implement with progress logging, run a gap audit, and record tweaks.
5linear-workflow
产品无关的 Linear 工作流，用于创建、更新、检查和讨论产品 issue、元数据、状态、范围、确认事项和长期产品文档同步。
4inline-doc-governance
Govern inline documentation coverage and comment quality in repo-owned source files. Use when Codex needs to audit or fix file headers, type docs, function or method contract docs, non-obvious inline comments, generated-file exclusions, or repo documentation rules for TypeScript, JavaScript, and Swift projects, including setting up a reusable docs/rules policy in a project-agnostic way.
2module-boundary-governance
Define, audit, and migrate module boundary manifests for codebases that need explicit ownership and dependency rules. Use when Codex is creating a new module, adding a new nested layer, moving code across layers, changing a module's public entrypoints, checking an existing repo's boundary health, or replacing weaker boundary docs and conventions with a canonical manifest-based system.
2