skills.rest
dawn840705
dawn840705COMMUNITY
Explore all skills by this author →
GitHub

changelog

Generate changelogs from git commits, sprint data, and design documents into internal and player-facing versions with versioning and traceability.

Updated Aug 27, 2026
Search Tags:#automation#git#changelog#documentation#sprint#release-notes#design-docs
One-click install
npx skills add https://github.com/dawn840705/claude-code-game-studios --skill changelog-dawn840705
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: changelog
Source: https://github.com/dawn840705/claude-code-game-studios/tree/main/skills/changelog
Command: npx skills add https://github.com/dawn840705/claude-code-game-studios --skill changelog-dawn840705

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the generation of changelogs from git commits, sprint reports, and design documents, providing both internal release notes and player-facing versions.

Core Features & Use Cases

  • Automated changelog generation: aggregates commits, sprint data, and design docs into a single changelog.
  • Dual-output: produces internal release notes for teams and a player-facing changelog for public consumption.
  • Versioning and traceability: supports version specifiers, sprint numbers, and references to design documents to provide context for changes.

Quick Start

Run the changelog generator to compile the latest commits, sprint data, and design documents into a formatted changelog.

Frequently Asked Questions about changelog

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

FAQPage Schema
How do I automatically generate changelogs from git commits and sprint data?▼

This process aggregates git history, sprint data from production/sprints, and design documents from design/gdd to automatically generate formatted changelogs with full version traceability.

Can I create separate release notes for internal teams and player-facing communications?▼

Yes, the system supports dual-output generation, producing both internal release notes for teams and a player-facing changelog for public communications from the same aggregated data.

What do I need to provide to generate release notes with sprint and design document traceability?▼

You need to provide access to your git history, sprint data stored in the production/sprints directory, and design documents located under design/gdd to generate traceable changelogs.

How are design documents integrated into automated changelog generation?▼

Design documents located under design/gdd are aggregated with git commits and sprint data to provide contextual references and traceability for specific changes within the generated changelog.

Does this changelog automation work for projects with regular releases and continuous design updates?▼

Yes, this automation is designed for software projects with regular releases and design updates, compiling version specifiers, sprint numbers, and design document references into formatted changelogs.

Related Skills

Explore More Content & Communication Skills→
HechaoYannetHechaoYannet

changelog

Generate internal and player-facing changelogs from git commits, sprint data, and design documents.

Community
Intermediate
plurigridplurigrid
60

changelog-generator

Generate user-facing changelogs from git commit history.

Official
Advanced
yonatangrossyonatangross
217

commit

Create Git commits following the Conventional Commits specification with local validation.

Community
Intermediate
imclabimclab
1

changelog

Generate internal and player-facing changelogs from git commits and sprint reports.

Official
Intermediate