Agent skill

asc-whats-new-writer

Generate engaging, localized App Store release notes (What's New) from git log, bullet points, or free text using canonical metadata under `./metadata`. Optionally pairs with promotional text updates.

rorkaigithub.com/rorkaiGitHub ↗
claude-codeMIT
Install
npx skills add rorkai/app-store-connect-cli-skills --skill asc-whats-new-writer --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 7 KB
Bundled scripts: none
Path: skills/asc-whats-new-writer/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 948
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# 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 login` or `ASC_*` env vars). - The **primary locale** is `en-US` unless the user specifies otherwise. ## Before You Start 1. Read `references/release_notes_guidelines.md` for tone, structure, and examples. 2. Identify the **latest version directory** under `metadata/version/` (highest semver). Use this for all metadata reads. 3. Enumerate **existing locales** by listing the JSON files in that version directory. ## Phase 1: Gather Input Accept one of three input modes (auto-detect): ### Git Log Parse commits since the last tag: ```bash # Find latest tag git describe --tags --abbrev=0 # List commits since that tag git log $(git describe --tags --abbrev=0)..HEAD --oneline --no-merges ``` Filter out noise: merge commits, dependency bumps, CI changes, formatting-only commits. Extract user-facing changes. ### Bullet Points User provides roug

What's inside
Steps it walks through
  1. Preconditions
  2. Before You Start
  3. Phase 1: Gather Input
  4. Git Log
  5. Bullet Points
  6. Free Text
  7. No Input Provided
  8. Phase 2: Draft Notes (Primary Locale)
  9. Step 1: Classify Changes
  10. Step 2: Write Benefit-Focused Copy
  11. Step 3: Front-Load the Hook
  12. Step 4: Echo Keywords for Conversion
  13. Step 5: Respect Character Limits
  14. Step 6: Optionally Draft Promotional Text
Ships with 1 file
  • references/release_notes_guidelines.md
Commands it runs
Find latest tag
git describe --tags --abbrev=0
List commits since that tag
git log $(git describe --tags --abbrev=0)..HEAD --oneline --no-merges
Individual locale direct update
asc apps info edit --app "APP_ID" --version-id "VERSION_ID" --locale "en-US" --whats-new "Your release notes here"
Bulk canonical-metadata push after writing ./metadata/version/<version>/<locale>.json
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"
More from app-store-connect-cli-skills
All skills →
About this skill
What does the asc-whats-new-writer skill do?

Generate engaging, localized App Store release notes (What's New) from git log, bullet points, or free text using canonical metadata under `./metadata`. Optionally pairs with promotional text updates.

How do I install it?

Run `npx skills add rorkai/app-store-connect-cli-skills --skill asc-whats-new-writer --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From rorkai/app-store-connect-cli-skills, a repository with 948 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going