changelog

Generate categorized release notes from git commits and sprint reports.

Updated May 13, 2026

Search Tags:#git #changelog #game development #versioning #release notes #patch notes #sprint reporting

Ready to run

npx skills add https://github.com/FrancisVarga/the-dream-machine --skill changelog-francisvarga

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: changelog
Source: https://github.com/FrancisVarga/the-dream-machine/tree/main/.claude/skills/changelog
Command: npx skills add https://github.com/FrancisVarga/the-dream-machine --skill changelog-francisvarga

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the manual work of turning scattered commits, sprint notes, and design docs into a clear changelog that both you and your players can understand.

Core Features & Use Cases

Automates internal + player-facing releases: Produces two changelog versions, with player language that avoids implementation details.
Builds context from multiple sources: Uses git history, sprint reports, and design documents to improve accuracy and narrative.
Supports version or sprint selection: Generates logs for a tagged release version or a sprint number range.

Example use case: You finish a sprint and want a polished public patch note that explains what’s new, what improved, and what changed in balancing—grounded in commit intent and design rationale.

Quick Start

Ask the changelog skill to generate an internal and player-facing changelog for version 1.2.3, then offer to write it 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 commits and sprint reports?▼

Generate release notes by selecting a git commit range from tags or sprint date windows, applying categorization heuristics to commit messages, and outputting categorized markdown. This transforms scattered history into structured patch notes.

Can I create separate patch notes for players and internal teams from the same git history?▼

Yes, this process creates both internal and player-facing changelogs from the same git history. The player-facing version uses accessible language that avoids implementation details, while the internal version retains technical specifics.

How do I categorize git commits into features, bug fixes, and balance changes for versioning?▼

Categorize commits by applying heuristics based on commit messages and task references. This groups git history into distinct release note categories like features, improvements, bug fixes, and balance changes automatically.

Does generating a changelog require a specific git repository setup?▼

Generating a changelog requires git availability checks to access commit history. You need a git repository with tagged releases or date windows to define the commit range for sprint-scoped or tag-scoped summaries.

What is the best way to document game development patch notes for a new release?▼

The best way to document game development patch notes is transforming git commits, sprint reports, and design documents into categorized release notes. This grounds the summary in commit intent and design rationale.

Can I write sprint-scoped changelogs directly to a markdown file?▼

Yes, you can write sprint-scoped or tag-scoped changelogs directly to docs/CHANGELOG.md. The final output is suitable markdown formatted for saving directly into your documentation directory.