store-changelog
Generate release notes for app stores (Android Play Store, iOS App Store, macOS App Store, Linux Flatpak). Use when the user asks for changelogs, release notes, or store descriptions based on git history.
Best use case
store-changelog is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Generate release notes for app stores (Android Play Store, iOS App Store, macOS App Store, Linux Flatpak). Use when the user asks for changelogs, release notes, or store descriptions based on git history.
Teams using store-changelog should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/store-changelog/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How store-changelog Compares
| Feature / Agent | store-changelog | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Generate release notes for app stores (Android Play Store, iOS App Store, macOS App Store, Linux Flatpak). Use when the user asks for changelogs, release notes, or store descriptions based on git history.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Store Changelog Generator
Generate release notes for App stores based on git history since a specified tag.
## Instructions
1. **Get the tag name**:
- If the user provides a tag name (e.g., `1.0.0` or `v1.0.0`), use it
- If not provided, automatically get the latest tag using: `git describe --tags --abbrev=0`
- Inform the user which tag is being used
2. **Analyze git history**: Run `git log <tag>..HEAD --pretty=format:"%h %s%n%b" --no-merges` to get all commits since the tag, including both commit messages and descriptions.
3. **Identify changes**: Categorize commits into:
- New features
- Improvements
- Bug fixes
4. **Generate platform-specific release notes** following the formats below.
## Output Formats
### Android (Play Store)
- Maximum 500 characters
- Bullet point format
- Focus on top 3-4 most impactful changes
- Example:
```
• New reader mode for distraction-free reading
• Improved sync reliability with FreshRSS
• Fixed crash when opening large feeds
```
### iOS (App Store)
- User-friendly narrative format
- Highlight iOS-specific improvements (scrolling, touch interactions, mobile layout)
- Group by: New Features, Improvements, Bug Fixes
- Example:
```
New Features:
• Reader mode now provides a clean, distraction-free reading experience.
Improvements:
• Smoother scrolling and faster feed loading on all devices.
Bug Fixes:
• Fixed an issue where the app could crash when opening feeds with many articles.
```
### macOS (App Store)
- User-friendly narrative format
- Highlight macOS-specific improvements (desktop layout, toolbar, keyboard shortcuts, interface)
- Separate from iOS since they are different apps
- Group by: New Features, Improvements, Bug Fixes
### Linux (Flatpak metainfo.xml)
- XML format with individual `<p>` tags
- Concise, one-line descriptions per change
- Format:
```xml
<release version="X.X.X" date="YYYY-MM-DD">
<description>
<p>Feature or fix description</p>
<p>Another change</p>
</description>
</release>
```
## Resources
- `references/release-notes-guidelines.md`: Language, filtering, and QA rules for App Store notes.Related Skills
wiki-changelog
Analyzes git commit history and generates structured changelogs categorized by change type. Use when the user asks about recent changes, wants a changelog, or needs to understand what changed in th...
review-changelog
Review and complete new changelog entries after automated PR creation. Use when there's a new changelog PR with entries that have placeholder URLs or empty fields that need review. Triggers on phrases like "review changelog", "complete changelog entries", "fix changelog PR", or when user mentions a PR with changelog updates.
project-orchestrator:changelog
Use when completing changes to any service - ensures standardized changelog entries with correct format, location, and content.
changelogator
Generate a changelog from git commits. Use when the user asks to generate a changelog, prepare release notes, summarize commits, prepare a release, suggest a version bump, or review changes since last tag. Also use when the user mentions "changelog", "release notes", "what changed", "version bump", or "semver".
changelog-update
Update CHANGELOG.md [Unreleased] section with business-focused entries via systematic file review
changelog-generator
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
changelog
Write changelog entries for Hugging Face Hub features. Use when asked to write a changelog, create a changelog entry, or document a new feature/PR for hf.co/changelog. Triggers on "write changelog", "changelog entry", "document this PR/feature for changelog".
changelog-automation
Automate changelog generation from commits, PRs, and releases following Keep a Changelog format. Use when setting up release workflows, generating release notes, or standardizing commit conventions.
app-store-changelog
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.
agent-changelog
Compile an agent-optimized changelog by cross-referencing git history with plans and documentation. Use when asked to "update changelog", "compile history", "document project evolution", or proactively after major milestones, architectural changes, or when stale/deprecated information is detected that could confuse coding agents.
acc-changelog-template
Generates CHANGELOG.md files following Keep a Changelog format. Creates version history documentation.
app-store
Master App Store deployment - Submission, TestFlight, CI/CD, release management