changelog

Generate internal and player-facing changelogs from Git commit history.

1|Updated May 5, 2026
One-click install
npx skills add https://github.com/XGanQAQ/Unity-Claude-Code-Game-Studios --skill changelog-xganqaq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog
Source: https://github.com/XGanQAQ/Unity-Claude-Code-Game-Studios/tree/main/.claude/skills/changelog
Command: npx skills add https://github.com/XGanQAQ/Unity-Claude-Code-Game-Studios --skill changelog-xganqaq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of turning messy Git history plus design and sprint context into a clear, ready-to-share changelog that you can maintain consistently.

Core Features & Use Cases

  • Auto-categorized internal changelog: Produces an internal write-up that groups changes into New Features, Improvements, Bug Fixes, Balance Changes, Technical Debt/Refactoring, Miscellaneous, and Known Issues.
  • Player-facing changelog: Converts the same work into a community-friendly format focused on player experience rather than implementation details.
  • Context-aware coverage: Supports generating changes for a specific release tag or for a sprint time window by reading sprint reports and design docs from the project.

Quick Start

Run the changelog skill for the desired version tag or sprint number and review the generated internal and player-facing changelog entries before writing them to docs/CHANGELOG.md.

Frequently Asked Questions about changelog

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

FAQPage Schema
How do I generate release notes from Git commit history?

Generating release notes from Git commit history involves parsing commit logs and categorizing them into structured groups. This Skill transforms commits, sprint reports, and design documents into structured internal and player-facing changelogs.

How do I create player-facing changelogs from internal sprint reports?

Creating player-facing changelogs from sprint reports converts technical implementation details into community-friendly messaging. This Skill reads your sprint context and generates output focused on player experience rather than internal logic.

Can I generate a changelog for a specific Git tag or sprint date range?

Generating a changelog for a specific Git tag or sprint date range is supported through two distinct workflows. You can isolate changes by release tag or collect commits within a targeted sprint time window.

Does Git changelog generation work for game development balance adjustments and bug fixes?

Git changelog generation works for game development by tracking features, improvements, bug fixes, and balance adjustments. It categorizes these specific changes from your commit history into dedicated internal write-ups.

How do I automatically categorize Git commits into New Features and Bug Fixes?

Automatically categorizing Git commits into New Features and Bug Fixes requires validating commit history and applying task-reference counting. This Skill structures changes into predefined categories including Technical Debt and Known Issues.

What is the best way to append generated changelogs to docs/CHANGELOG.md?

Appending generated changelogs to docs/CHANGELOG.md is handled natively by this Skill. After reviewing the internal and community-ready messaging, you can optionally append or overwrite the file directly during generation.