agentsclimarketplace
Sign in

Appstore release notes writer

Skill Xopoko/build-swift-apps/skills/appstore-release-notes-writer

Use when the requested App Store artifact is What's New release notes or promotional text, drafted from git history, bullets, or free text and optionally localized. Not for full listing translation, canonical metadata field sync, or subscription/IAP display names.From its SKILL.md

Install
npx -y skills add Xopoko/build-swift-apps --skill appstore-release-notes-writer

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • reads credentialsReads from 1 credential source: `metadata/version/{latest-version}/{locale}.json`.
  • runs commandsInstructs the agent to run 5 commands, including `git describe --tags --abbrev=0` and 4 more.

SKILL.md

3.1 KB, 683 tokens by cl100k_base, as published. Nobody here has run it

App Store Release Notes Writer

Write human-focused release notes, optionally localized to every existing metadata locale.

Use appstore-metadata-sync for general listing metadata edits, appstore-metadata-localizer for full listing translation, and appstore-subscription-localizer for subscription/IAP display-name localization.

Preconditions

  • Canonical metadata from asc metadata pull --app "APP_ID" --version "1.2.3" --dir "./metadata" or user-provided keywords.
  • Auth configured for upload.
  • Primary locale is en-US unless specified.
  • Read references/release_notes_guidelines.md.
  • Use highest semver under metadata/version/; locales are the JSON files there.

Workflow

  1. Gather input:
    • Git log: git describe --tags --abbrev=0 then git log <tag>..HEAD --oneline --no-merges; remove merges/deps/CI/format noise.
    • User bullets or free text.
    • If absent, ask what changed.
  2. Classify user-visible changes into New, Improved, Fixed; omit empty sections.
  3. Draft primary locale notes:
    • lead with the clearest user-facing hook in the first ~170 chars;
    • describe user impact, not implementation;
    • use concrete action verbs;
    • naturally echo relevant local keywords from metadata/version/<version>/<locale>.json when present;
    • target 500-1500 chars, hard limit 4000.
  4. If requested, draft promotionalText <= 170 chars.
  5. Show draft with character count and wait for approval before localizing.
  6. Localize approved notes:
    • formal/professional register and formal "you" where applicable;
    • adapt idioms and tone to local market;
    • echo locale-specific keywords naturally;
    • validate What's New <= 4000 and promo <= 170; shorten, never truncate mid-sentence.
  7. Present a locale table with first 80 chars, counts, promo text/counts; wait for upload approval.
  8. Upload: 
    asc apps info edit --app "APP_ID" --version-id "VERSION_ID" --locale "en-US" --whats-new "..."
asc metadata push --app "APP_ID" --version "1.2.3" --dir "./metadata" --dry-run
asc metadata push --app "APP_ID" --version "1.2.3" --dir "./metadata"
    Include promo via --promotional-text or write promotionalText into canonical JSON before push.

Paths

  • Keywords/current notes: metadata/version/{latest-version}/{locale}.json
  • Fields: keywords, whatsNew, optional promotionalText
  • Canonical tree is shared with asc metadata pull/push/keywords.

Rules

  • What's New is not App Store search-indexed; write for conversion and clarity.
  • Promotional text can update without a new submission.
  • The visible 170-char preview matters most.
  • On partial upload failure, report successes/failures and retry failed locales only.
  • Use appstore-metadata-localizer for full listing translation and appstore-aso-auditor for keyword research.

What ships with it: 1 file

5.0 KB alongside SKILL.md

references/

Gives 0 of the 12 instructions most ship operate skills give in 683 tokens

Counted across 1,077 of the 1,713 authors here whose files we hold, read 2026-09-06

  • Create GitHub releasein 44 of 1077, across 43 files
  • Run the test suitein 30 of 1077, across 25 files
  • Create and push git tagin 27 of 1077, across 26 files
  • Push commits and tagsin 27 of 1077
  • Create annotated tagin 25 of 1077, across 22 files
  • Ensure working tree is cleanin 24 of 1077
  • Check for product marketing context firstin 23 of 1077, across 6 files
  • Commit version bump changesin 22 of 1077, across 21 files
  • Update CHANGELOG.mdin 21 of 1077, across 20 files
  • Structure launch marketing across three channel typesin 20 of 1077, across 5 files
  • Commit and tag the releasein 20 of 1077, across 18 files
  • Update the CHANGELOG for new releasesin 19 of 1077

Said here and by no other author read

  • Gather input from git log or user text
  • Classify changes into New, Improved, and Fixed
  • Lead with a clear user-facing hook
  • Describe user impact instead of implementation
  • Use concrete action verbs in the draft
  • Target between 500 and 1500 characters

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.