What problem does it solve? Writing release notes means translating the same set of commits into two very different voices: detailed technical notes for developers and short, benefit-led copy for app store users. Doing both manually is slow and often produces jargon-filled store listings or vague changelogs. ## Core Features & Use Cases - Dual-output generation: Produces a Keep a Changelog entry, GitHub release body, and PR description alongside Play Store/App Store "what's new" copy (max 500 chars, Korean and English) and a one-line in-app banner in a single pass. - Commit classification: Reads the actual git log and diff between tags, then separates user-visible changes (features, impactful fixes) from internal-only work (refactors, dependency bumps, CI) so store copy never leaks technical noise. - Human-voice guard: Strips marketing clichés, AI-sounding phrasing, and emoji overload from user-facing text, optionally delegating to a human-voice-guard skill. - Use Case: After tagging v1.4.0, ask for release notes and receive a ready-to-paste CHANGELOG entry, GitHub release body, and Korean/English store listings that describe benefits rather than commit messages. ## Quick Start Ask the assistant to write release notes for the changes between the previous git tag and HEAD, covering both the GitHub release and the Play Store update text.
