changelog

Generate categorized release notes from git history for internal and player audiences.

Updated Mar 28, 2026
One-click install
npx skills add https://github.com/scomofo/dragon-forge --skill changelog-scomofo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog
Source: https://github.com/scomofo/dragon-forge/tree/main/.agents/skills/changelog
Command: npx skills add https://github.com/scomofo/dragon-forge --skill changelog-scomofo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns noisy git history, sprint reports, and design notes into clear, review-ready changelog entries for both internal teams and players.

Core Features & Use Cases

  • Auto-categorize change types: Groups commits into New Features, Improvements, Bug Fixes, Balance Changes, Technical Debt/Refactoring, Miscellaneous, and Known Issues using commit messages and task/story references.
  • Version- or sprint-scoped reporting: Builds the changelog for either a specific version (via git tags) or a sprint time window (via sprint date ranges).
  • Two audiences, two outputs: Produces an internal changelog with technical/ownership metrics and a player-facing patch notes draft focused on user-visible outcomes and intent.

Quick Start

Run the changelog skill with a target version or sprint number to generate both the internal and player-facing changelog text.

Frequently Asked Questions about changelog

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

FAQPage Schema
How do I generate patch notes from git commit history for a game release?

You can generate patch notes by processing git commit history and sprint documentation through categorization logic. The Skill groups commits into New Features, Bug Fixes, and Balance Changes to produce both internal technical reports and player-facing patch note drafts.

What is the best way to create internal and player-facing changelogs from sprint reports?

Creating internal and player-facing changelogs from sprint reports involves parsing sprint date ranges and design documents. The Skill categorizes these changes into structured release notes, providing technical ownership metrics for developers and intent-focused outcomes for players.

Can I scope changelog generation to a specific git tag or sprint time window?

Yes, you can scope changelog generation to a specific version or sprint time window. The Skill requires argument parsing for version-tagged releases or sprint-window date ranges to determine the exact commit range for your categorized release notes.

How does commit categorization work for game development release notes?

Commit categorization for game development release notes works by analyzing commit messages and task-story references. The Skill automatically groups changes into categories like New Features, Improvements, Bug Fixes, Balance Changes, Technical Debt, and Known Issues.

Do I need a specific git repository setup to generate sprint reporting changelogs?

Yes, you need a git repository setup to generate sprint reporting changelogs. The Skill requires git repository verification to determine the commit range accurately, relying on version tags or sprint date ranges to extract the relevant history.