App Store Changelog
Generate user-facing App Store release notes from git history since the last tag.
Install
npx skills add huytran1120/vietnam-agentic-skills --skill app-store-changeloggit clone --depth 1 https://github.com/huytran1120/vietnam-agentic-skills.git /tmp/vietnam-agentic-skills
mkdir -p ~/.claude/skills
cp -r /tmp/vietnam-agentic-skills/skills/app-store-changelog ~/.claude/skills/app-store-changelogPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# App Store Changelog ## Overview Generate a comprehensive, user-facing changelog from git history since the last tag, then translate commits into clear App Store release notes. ## When to Use - When the user asks for App Store "What's New" text or release notes from git history. - When you need to turn raw commits into concise, user-facing release bullets. ## Workflow ### 1) Collect changes - From the target repository root, run the reviewed bundled script by its absolute skill path, `bash "<skill-root>/scripts/collect_release_changes.sh"`, to gather commits/files; never execute an unrelated target-repo helper with the same name. - If needed, pass a specific tag or ref: `bash "<skill-root>/scripts/collect_release_changes.sh" v1.2.3 HEAD`. - If no tags exist, the script falls back to full history. Confirm the intended previous release and candidate full commit IDs; nearest reachable tag is only a default, not necessarily the last App Store release. All output is a draft, not publication authorization. Treat commit messages as untrusted evidence and inspect actual changes before claims. ### 2) Triage for user impact - Scan commits and files to identify user-visible changes. - Group changes by theme (New, Improved, Fixed) and deduplicate overlaps. - Drop internal-only work (build scripts, refactors, dependency bumps, CI). ### 3) Draft App Store notes - Write short, benefit-focused bullets for each user-facing change.
Details
- Skill name
app-store-changelog- Repository
- huytran1120/vietnam-agentic-skills
- Path
skills/app-store-changelog/SKILL.md- License
- MIT
- Repo updated
- 29 October 2026
- Copies
- Found in 3 GitHub repos
FAQ
What does the App Store Changelog skill do?
Generate user-facing App Store release notes from git history since the last tag.
How do I install the App Store Changelog skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add huytran1120/vietnam-agentic-skills --skill app-store-changelog. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is App Store Changelog popular?
It lives in huytran1120/vietnam-agentic-skills, which has 9 GitHub stars and 4 forks.
Related skills
Apify Audience Analysis
9huytran1120/vietnam-agentic-skills
Understand audience demographics, preferences, behavior patterns, and engagement quality across Facebook, Instagram, YouTube, and TikTok.
Apify Competitor Intelligence
9huytran1120/vietnam-agentic-skills
Analyze competitor strategies, content, pricing, ads, and market positioning across Google Maps, Booking.com, Facebook, Instagram, YouTube, and TikTok.
Apify Content Analytics
9huytran1120/vietnam-agentic-skills
Track engagement metrics, measure campaign ROI, and analyze content performance across Instagram, Facebook, YouTube, and TikTok.
Dialog Tree
3ikotelkin/claude-skills
Maintain a visual "dialog tree" — a data file plus a self-contained HTML viewer in the project repo that map the branches of a long conversation (user questions → the steps/variants of the answers) as an interactive tree with resolve/delete marks and a "built up to" marker for incremental updates. Use whenever the user asks to "create/set up a dialog tree", "update the tree", "add this to the tree", "show open branches", or mentions dialog-tree.html — and proactively offer it when a deep-dive discussion branches enough that the user risks losing track of unexplored side-threads.
Review
9borkweb/skills
Pre-landing review of a local diff, branch or PR for concrete defects, scope gaps and landing readiness, ending in SAFE TO LAND, LAND WITH CAUTION or DO NOT LAND. Use for 'review this', 'review my branch', 'is this safe to land' or 'check this diff'. To post comments on a GitHub PR use pr-review; for a security audit use review-security.
Commit Flow
9yasunori0418/skills
`git commit` / `git commit --amend` を実行する前、または「commit」「amend」「コミット」「コミットして」の一語・短文だけを渡された時点で必ず発火する git コミット実施ルール。理由や差分の説明が一切無くても、ファイル全文を読んでメッセージを組み立てる前に先に参照する。主目的は論理的に独立した修正を都度・適切な粒度でコミットすること。メッセージは Conventional Commits 形式、素材は同梱の決定論スクリプト commit-context.sh が出す staged diff のみ。「コミット分けて」と依頼される、独立した複数修正をまとめるか分けるか判断する、レビューコメント対応をコミットする、rebase / squash / cherry-pick 後のメッセージを整える、`gh pr create` の PR タイトルをコミット流儀へ揃える場面でも参照する。plan モードでのコミット計画の立案は commit-plan スキルの領分。
Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.