happier-release-notes

To generate release notes from git commit history, the skill clusters commits by user-facing outcomes and filters out non-user-visible changes. It then proposes structured markdown content and a StoryDeck card set before baking the approved version into a release JSON manifest.

Creating StoryDeck cards for a UI changelog involves producing a short list, image, and video card set aligned to the app’s card contract limits. The skill drafts this content directly from final author input or parsed git tag diffs.

Yes, you can validate translation keys and asset references in release markdown. The skill runs a release-note parsing pipeline that confirms all references are correctly wired and ensures changes land only in expected generated manifests.

The best way to bundle offline-safe media is to organize image cards and video posters for bundled use while staging heavier optional media under a release assets boundary. This ensures the UI deck loads correctly without external network dependencies.

Yes, this release-note generation method works with both tag diffs and final author copy. It accepts raw release inputs from final copy, git diffs, commits, or tags and turns them into polished, publish-ready markdown and JSON outputs.

You should not rely solely on automated git analysis for release notes when your commits lack descriptive user-facing context. In those cases, provide final author copy directly so the skill can curate accurate StoryDeck content without misleading generated outcomes.