
App Store Changelog
FreeGenerate user-friendly release notes from git history.
Free · Opens the source repo
What App Store Changelog does
The App Store Changelog skill automates the generation of user-facing release notes directly from your git history, specifically since the last tagged version. This skill is particularly useful for developers and product managers who need to quickly create concise, informative updates for App Store submissions. By leveraging your existing commit messages, it transforms technical jargon into clear, benefit-focused bullet points that are suitable for end users.
To use this skill, you begin by running the provided script collect_release_changes.sh, which gathers all relevant commits and files since the last tag. If no tags are present, it defaults to the full commit history. The skill then analyzes these changes, filtering out internal updates that do not affect users, and organizes the remaining changes into categories such as New, Improved, and Fixed. This triage process ensures that only the most relevant updates are communicated to your users.
Once the changes are categorized, the skill drafts the App Store release notes, focusing on clarity and user impact. Each bullet point is crafted to highlight the benefits of the changes made, ensuring that they resonate with users. The output format adheres to App Store guidelines, typically preferring 5 to 10 concise bullets that summarize the key updates. This structured approach not only saves time but also enhances the quality of communication with your users.
Overall, the App Store Changelog skill is an essential tool for any developer looking to streamline the release note creation process, ensuring that updates are communicated effectively and efficiently to users.
When to use it
Use this skill when you need to create App Store release notes based on recent changes in your codebase.
When not to use it
Avoid using this skill if your project does not use git or if you require highly customized release notes that cannot be generated from commit messages.
What you can build with it
Quick Release Notes Generation
A developer needs to submit an app update and uses the skill to quickly generate concise release notes from recent commits.
Filtering Internal Changes
A product manager runs the skill to ensure that only user-visible changes are included in the release notes, excluding internal refactors.
Streamlining App Store Submissions
A team regularly submits updates to the App Store and uses this skill to automate the documentation process, saving time and effort.
How to install App Store Changelog
View source1. Install with the skills CLI
npx skills add sickn33/agentic-awesome-skills/app-store-changelog --agent claude-code2. Or install it manually
Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.
Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs
Inside SKILL.md
Written by sickn33App 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
- Run
scripts/collect_release_changes.shfrom the repo root to gather commits and touched files. - If needed, pass a specific tag or ref:
scripts/collect_release_changes.sh v1.2.3 HEAD. - If no tags exist, the script falls back to full history.
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.
- Use clear verbs and plain language; avoid internal jargon.
- Prefer 5 to 10 bullets unless the user requests a different length.
4) Validate
- Ensure every bullet maps back to a real change in the range.
- Check for duplicates and overly technical wording.
- Ask for clarification if any change is ambiguous or possibly internal-only.
Commit-to-Bullet Examples
The following shows how raw commits are translated into App Store bullets:
| Raw commit message | App Store bullet |
|---|---|
fix(auth): resolve token refresh race condition on iOS 17 | • Fixed a login issue that could leave some users unexpectedly signed out. |
feat(search): add voice input to search bar | • Search your library hands-free with the new voice input option. |
perf(timeline): lazy-load images to reduce scroll jank | • Scrolling through your timeline is now smoother and faster. |
Internal-only commits that are dropped (no user impact):
chore: upgrade fastlane to 2.219refactor(network): extract URLSession wrapper into moduleci: add nightly build job
Example Output
What's New in Version 3.4
• Search your library hands-free with the new voice input option.
• Scrolling through your timeline is now smoother and faster.
• Fixed a login issue that could leave some users unexpectedly signed out.
• Added dark-mode support to the settings screen.
• Improved load times when opening large photo albums.
Output Format
- Title (optional): "What's New" or product name + version.
- Bullet list only; one sentence per bullet.
- Stick to storefront limits if the user provides one.
Resources
scripts/collect_release_changes.sh: Collect commits and touched files since last tag.references/release-notes-guidelines.md: Language, filtering, and QA rules for App Store notes.
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
Frequently asked questions about App Store Changelog
Similar skills
Markdown to HTML Conversion
Efficiently convert Markdown documents to HTML.
Code Tour
Create structured walkthroughs for codebases.
Acquire Codebase Knowledge
Streamline onboarding with comprehensive codebase documentation.
Documentation & Modernization
Streamline codebase documentation and modernization planning.
Azure Resource Visualizer
Generate architecture diagrams for Azure resources.
CLAUDE.md Improver
Optimize your CLAUDE.md files for better project context.
