Skip to content
Get packs

Changelog Generator

Writes internal and player-facing changelogs from git commits and sprint notes

Source Download skill
Repository
Donchitos/Claude-Code-Game-Studios
Stars
32,965
Licence
MIT
Files
1 file

What it does

When invoked, the agent reads recent git commits, tags and sprint reports for a game project and drafts a changelog grouped into categories like new features, bug fixes and balance changes. It includes an internal version for the team and a player-facing version. Before writing, it checks whether the commit history actually belongs to the game, and it stops rather than publishing framework-maintenance commits as player-facing release notes.

Great for

  • Game studios using the Claude Code Game Studios framework who need release notes drafted from commit history
  • Producers or developers preparing a version or sprint summary

Skip it if

  • Projects without meaningful git history or commit messages, since the output will be vague or blocked
  • Anyone wanting fully automatic publishing of player-facing notes without reviewing them, because the generated copy can still misstate changes

Try asking

  • “/changelog 1.2.0 to generate the changelog for the 1.2.0 tag”
  • “/changelog sprint-5 to summarise work from sprint 5”
  • “Generate an internal changelog and a player-facing changelog for the latest release”
Step-by-step guide: how to use Changelog GeneratorInstall, first run, examples, tips and FAQs

Install in 3 steps

  1. 1

    Download the skill

    The ZIP contains the 1 original files, the MIT licence and an attribution note.

    changelog.zip
  2. 2

    Add it to your agent

    Claude Code (all projects)

    mkdir -p ~/.claude/skills && unzip changelog.zip -d ~/.claude/skills/

    Claude Code / Agent SDK (this project only)

    mkdir -p .claude/skills && unzip changelog.zip -d .claude/skills/

    Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.

  3. 3

    Ask for the task

    No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.

Get better results

  • Tag releases before running it so the commit range is bounded to one release
  • Review the player-facing draft carefully, especially bug-fix wording, before sharing it
  • Keep commit messages descriptive and include task IDs so categorisation is more reliable

What's inside

  • SKILL.md

Redistributed unmodified from Donchitos/Claude-Code-Game-Studios under the MIT licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.