changelog

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

1|Updated May 15, 2026
One-click install
npx skills add https://github.com/dnkrow/skill --skill changelog-dnkrow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog
Source: https://github.com/dnkrow/skill/tree/main/claude-global/changelog
Command: npx skills add https://github.com/dnkrow/skill --skill changelog-dnkrow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of turning scattered development activity—like recent commits, sprint reports, and design decisions—into a clear, reviewable changelog for both internal teams and players.

Core Features & Use Cases

  • Git-based changelog generation: Builds an organized changelog from recent git commits and tags, supporting version or sprint-number targeting.
  • Context-aware classification: Categorizes changes into New Features, Improvements, Bug Fixes, Balance Changes, Technical Debt, Miscellaneous, and Known Issues, and tracks how many commits lack task references.
  • Dual output for different audiences: Produces an internal technical changelog and a player-facing patch notes draft with guidelines to avoid leaking internals.

Quick Start

Run the changelog skill to generate an internal and player-facing patch note draft for the latest version.

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 history and sprint reports?

You can generate player-facing patch notes by running the skill against version-tagged releases; it creates a community-safe draft that applies formatting guidelines to avoid leaking internal technical details.

Can I categorize git commits into New Features and Bug Fixes for release notes?

You need access to git log and tags, sprint data stored in production/sprints/, and design documents located in design/gdd/ to successfully generate the categorized internal and player-facing changelogs.

What's the best way to create community-safe patch notes from development commits?

The best way to create community-safe patch notes is to use the skill's dual-output feature, which generates an internal technical changelog alongside a player-facing draft designed to avoid leaking internals.

How does the changelog skill handle commits that lack task references?

The skill targets version-tagged releases or sprint-number periods, requiring you to specify the version tag or sprint number to extract the corresponding development activity for structured summarization.

What limitations exist when generating sprint reports into categorized release notes?

A limitation is that generating categorized release notes requires deterministic formatting and access to specific directory structures like design/gdd/ and production/sprints/, meaning incomplete git logs or missing sprint data will reduce output accuracy.