How do I install the Store Changelog skill?

Run npx skillmds@latest add tomevault-io/store-changelog in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Store Changelog safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Store Changelog?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Store Changelog free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Store Changelog?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Store Changelog by tomevault-io — Agent Skill

Name: Store Changelog
Author: tomevault-io

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. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

Store Changelog Generator

Generate release notes for App stores based on git history since a specified tag.

Instructions

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
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.
Identify changes: Categorize commits into:
- New features
- Improvements
- Bug fixes
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  tags
Concise, one-line descriptions per change

Format:

<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.

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: store-changelogdescription: 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. Use when this capability is needed.---# Store Changelog GeneratorGenerate release notes for App stores based on git history since a specified tag.## Instructions1. **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 used2. **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 fixes4. **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 `` tags- Concise, one-line descriptions per change- Format: ```xml <release version="X.X.X" date="YYYY-MM-DD"> <description> Feature or fix description Another change </description> </release> ```## Resources- `references/release-notes-guidelines.md`: Language, filtering, and QA rules for App Store notes.---> Converted and distributed by [TomeVault](https://tomevault.io/claim/prof18) — claim your Tome and manage your conversions.

Frequently asked questions