app-store-changelog
Skill430 starsChanged 6 months agoMITView on GitHub
Create user-facing App Store release notes by collecting and summarizing all user-impacting changes since the last git tag (or a specified ref). Use when asked to generate a comprehensive release changelog, App Store "What's New" text, or release notes based on git history or tags.
11 other projects use a version of this, 9 of them edited.
Adopted by
Most recently taken up by
- sambulosenda/Skillsedited, first seen Nov 8, 2026
- VelimirMueller/claude-skillsedited, first seen Nov 1, 2026
- VelimirMueller/ai-development-skillsedited, first seen Nov 1, 2026
- deonmenezes/mobile-app-skilledited, first seen Nov 1, 2026
- Vvlladd/iOSskillsCollectionedited, first seen Oct 13, 2026
- Samueladewole/claude-skillsword for word, first seen Oct 13, 2026
Used with
Projects with it also use swiftui-liquid-glass and ios-debugger-agent.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
OpenAISkillswiftui-liquid-glass
Implement and review iOS 26+ SwiftUI Liquid Glass UI. Use when adopting Liquid Glass or checking its correctness, performance, and design fit.
Also in 4 projects that use this
- OpenAISkill
ios-debugger-agent
Build, run, and debug iOS apps on Simulator with XcodeBuildMCP. Use when launching an app, inspecting simulator UI or logs, or diagnosing runtime behavior.
Also in 3 projects that use this
Other versions11 projects use a version of this.
Word for word · 2
- ParkerRex/Skills★ 2100% same
- Samueladewole/claude-skills★ 0100% same
Edited · 9
- Dimillian/Skills★ 4k65% same
- patrickserrano/skills★ 1314% same
- VelimirMueller/ai-development-skills★ 762% same
- VelimirMueller/claude-skills★ 762% same
- deonmenezes/mobile-app-skill★ 465% same
- Adhamxon/claude-code-skills★ 265% same
- sambulosenda/Skills★ 219% same
- Gold240sx/Skills★ 160% same
- Vvlladd/iOSskillsCollection★ 162% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository18 other files it gives its agents.
- AGENTS.mdAGENTS.md
- macos/AGENTS.mdAGENTS.md
- sandbox-vm/AGENTS.mdAGENTS.md
- web/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- macos/CLAUDE.mdCLAUDE.md
- sandbox-vm/CLAUDE.mdCLAUDE.md
- bridge-agent-log-analyzerSkill
- gh-issue-fix-flowSkill
- githubSkill
- react-component-performanceSkill
- swift-concurrency-expertSkill
- swift-concurrencySkill
- swift-testing-expertSkill
- swiftui-expert-skillSkill
- swiftui-performance-auditSkill
- swiftui-ui-patternsSkill
- swiftui-view-refactorSkill
The file
We split this skill into the rules it gives an agent
9 rules. 7 are common, 0 are distinctive, and 2 are very specific to this project.
7
Common
Most of the 9 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Run scripts/collect_release_changes.sh from the repo root to gather commits and touched files.
- Very specific: line 15
If needed, pass a specific tag or ref: scripts/collect_release_changes.sh v1.2.3 HEAD.
- Common: line 16
If no tags exist, the script falls back to full history.
- Common: line 24
Write short, benefit-focused bullets for each user-facing change.
- Common: line 25
Use clear verbs and plain language.
- Common: line 26
Prefer 5 to 10 bullets unless the user requests a different length.
- Common: line 29
Ensure every bullet maps back to a real change in the range.
- Common: line 30
Check for duplicates and overly technical wording.
- Common: line 31
Ask for clarification if any change is ambiguous or possibly internal-only.
“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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.
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.
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.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.