asc-whats-new-writer
asc What's New Writer
Generate engaging, localized release notes from flexible input. Optionally pair with promotional text updates.
Preconditions
- Metadata pulled locally into canonical files via
asc metadata pull --app "APP_ID" --version "1.2.3" --dir "./metadata". OR: user provides keywords manually. - Auth configured for upload (
asc auth loginorASC_*env vars). - The primary locale is
en-USunless the user specifies otherwise.
Before You Start
- Read
references/release_notes_guidelines.mdfor tone, structure, and examples. - Identify the latest version directory under
metadata/version/(highest semver). Use this for all metadata reads. - Enumerate existing locales by listing the JSON files in that version directory.
Phase 1: Gather Input
Accept one of three input modes (auto-detect):
More from rudrankriyam/asc-skills
asc-cli-usage
Guidance for using asc cli in this repo (flags, output formats, pagination, auth, and discovery). Use when asked to run or design asc commands or interact with App Store Connect via the CLI.
762asc-metadata-sync
Sync, validate, and apply App Store metadata with the current asc canonical metadata workflow. Use when updating metadata, localizations, keywords, or migrating legacy fastlane metadata.
715asc-id-resolver
Resolve App Store Connect IDs (apps, builds, versions, groups, testers) from human-friendly names using asc. Use when commands require IDs.
695asc-release-flow
Determine whether an app is ready to submit, then drive the current App Store release flow with asc, including validation, staging, review submission, first-time availability, subscriptions, IAP, Game Center, and App Privacy checks.
695asc-submission-health
Validate App Store submission readiness, submit prepared versions, and monitor review status with current asc commands. Use when shipping or troubleshooting review submissions.
689asc-testflight-orchestration
Orchestrate TestFlight distribution, groups, testers, and What to Test notes using asc. Use when rolling out betas.
679