ios-appstore-release-manager

iOS App Store Release Manager

Keep release-specific data in the project's docs/app-store-connect/releases/ directory. Keep this Skill limited to workflow, schema, and tooling.

Read references/release-form-schema.md before creating, validating, translating, or filling a release. Read references/aso-handoff-schema.md before importing ASO copy. Read references/release-version-table.md when comparing existing versions or adding a new version row.

Workflow

1. Locate the repository root and determine whether it is Flutter or native Xcode. Prefer explicit --version plus --build, then Flutter pubspec.yaml, then Xcode build settings. Never guess among multiple workspaces, projects, or schemes; request --workspace, --project, or --scheme.
2. Choose the translation source locale with the user. Use any App Store Connect locale as the source; default to zh-Hans only when the user has no preference. Run python3 <skill-dir>/scripts/release_form.py new --repo <repo> --source-locale <locale> when a form does not exist. It reads the current version/build, finds the latest previous form, and creates a schema 8 draft.
3. If $app-store-aso produced an aso-handoff.json, import it only after validation with python3 <skill-dir>/scripts/release_form.py import-aso <handoff> <form>. Import only description, promotional text, keywords, and What's New. Keep App Name and Subtitle as App Information recommendations; never write them automatically.
4. Review Git changes and model configuration to draft four source-language fields: 描述, 推广文本, 关键词, and 此版本的新增内容.
5. Show all four drafts in the selected source language to the user. Track their approval independently. Do not translate or fill any public copy until all four are explicitly approved.
6. Open the App Store Connect language selector and inventory every language shown under both the localized and unlocalized groups. Record their union in locale_inventory and preserve each locale's current inventory state.
7. Before translating or filling any locale, perform both mandatory preflight confirmations:
   • Inspect the current session's available Skills and tools for computer-use:computer-use. Report whether it is available and record computer_use_availability in the form. Never assume availability from an earlier run.
   • Show the localized and unlocalized locale counts, then explicitly ask whether the user wants to translate and create the currently unlocalized languages. Do not infer the choice from a prior release. Record unlocalized_locale_policy and set localization_scope to either app_store_connect_localized_languages or app_store_connect_all_languages.
8. Generate all four localized fields only for the confirmed scope, including a translated description in every included locale. Mark excluded unlocalized locales not_requested_by_user with page strategy not_in_scope; do not create, translate, or edit them. Use the active language model's own multilingual capability by default; translation must not depend on an external translation API, browser translation feature, network access, or third-party account. Only use an external translation service when the user explicitly requests that service. Keywords must be localized ASCII-comma-separated search terms, not sentence translations.
9. Before editing each in-scope field, read its current App Store Connect value and compare normalized text. If the page is empty, write the translation; if it matches, keep it; if it contains different content, pause and ask the user whether to inherit the existing value or replace it with this translation. Never make that conflict choice silently.
10. Run python3 <skill-dir>/scripts/release_form.py validate <form> --repo <repo>. Resolve errors before browser automation and report warnings requiring human judgment.
11. When Computer Use is available, use it with the user's existing Chrome login. If it is unavailable, state that clearly and use an available supported browser-control capability only after recording the fallback. Re-read the page before every edit. For each in-scope locale, inspect description, promotional text, keywords, and What's New before typing. Resolve every differing non-empty value with the user, then apply the recorded per-field strategy, save, and read all four displayed values back.
12. Select only a build whose Apple processing is complete. Save the draft and verify the binding.
13. Stop before Add for Review, Submit for Review, or any equivalent submission control. Report completed fields, excluded unlocalized languages, and remaining manual checks.
14. Add or update the version row in references/release-version-table.md, recording field status and inheritance without copying sensitive information.