changelog

Generate App Store release notes from commits between the latest tag and HEAD.

105|10|Updated Nov 15, 2025
One-click install
npx skills add https://github.com/everpcpc/KMReader --skill changelog-everpcpc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog
Source: https://github.com/everpcpc/KMReader/tree/main/.agents/skills/changelog
Command: npx skills add https://github.com/everpcpc/KMReader --skill changelog-everpcpc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically converts commit history into clear, user-facing App Store release notes, saving time drafting notes and ensuring consistency across releases.

Core Features & Use Cases

  • Convert full commit bodies into narrative release notes with sections suitable for App Store.
  • Maintain readability by rewording technical details into user-friendly language while preserving key changes.
  • Use for release cycles to generate end-user notes from the latest tag to HEAD, including important bug fixes and enhancements.

Quick Start

Generate release notes for the next App Store update by processing commits from the latest tag to HEAD.

Frequently Asked Questions about changelog

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate user-facing release notes from git commits?

To generate release notes from git commits, this skill processes the full commit bodies between your latest tag and HEAD, rewording technical implementation details into structured, readable App Store changelog text for end users.

How does commit history conversion work for App Store changelogs?

Commit history conversion works by extracting full commit bodies from the latest tag to HEAD, rewording technical details into user-friendly language, and structuring the output into readable sections suitable for an App Store changelog.

Can I use this to automate release notes generation for software apps?

Yes, you can automate release notes generation for software apps by processing the commits between your latest tag and HEAD, automatically converting the commit history into consistent, structured changelog text for end users.

What is the best way to turn technical commit details into plain language release notes?

The best way to turn technical commit details into plain language release notes is to process full commit bodies and reword the technical implementation details into user-friendly language while preserving key changes in a structured format.

Does this changelog generator include technical implementation details in the output?

No, this changelog generator specifically excludes technical implementation details from the final output, focusing instead on rewording commit history into user-friendly, sectioned language for App Store release notes.