skills.rest
HechaoYannet
HechaoYannetCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

changelog

Generate internal and player-facing changelogs from git commits, sprint data, and design documents.

Updated Apr 8, 2026
Search Tags:#automation#git#changelog#documentation#sprints#release-notes#design-docs
One-click install
npx skills add https://github.com/HechaoYannet/3kingdom-unity --skill changelog-hechaoyannet
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: changelog
Source: https://github.com/HechaoYannet/3kingdom-unity/tree/main/.claude/skills/changelog
Command: npx skills add https://github.com/HechaoYannet/3kingdom-unity --skill changelog-hechaoyannet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Changelog generation is time-consuming and error-prone when consolidating commits, sprint notes, and design decisions. This skill automates that process, producing accurate internal records and reader-friendly release notes.

Core Features & Use Cases

  • Internal changelogs: Generate technical summaries for engineering teams.
  • Player-facing release notes: Create customer-facing notes ready for publishing.
  • Version-focused reports: Align commits, sprint outcomes, and design changes by version.

Quick Start

Run the changelog generator for the current release to produce both internal and player-facing notes.

Frequently Asked Questions about changelog

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

FAQPage Schema
How do I automate changelog generation from git commits and sprint data?▼

Access git history, sprint reports in production/sprints, and design docs in design/gdd to generate internal changelogs and player-facing notes. The generator requires these specific directory structures and commit data to align version-focused reports.

Can I create both internal changelogs and player-facing release notes from git history?▼

Internal changelogs provide technical engineering summaries, while player-facing release notes are customer-facing and ready for publishing. The tool outputs both structures simultaneously from git commits, sprint data, and design documents.

What's the best way to consolidate design documents and git commits into release notes?▼

Run the changelog generator during release cycles to extract design decisions from design/gdd and cross-reference them with commit history. This produces accurate version-focused reports that align sprint outcomes with technical changes.

Do I need specific directory structures for sprint reports and design docs to generate changelogs?▼

Sprint reports must reside in production/sprints and design docs in design/gdd. The generator accesses these specific paths to consolidate sprint outcomes and design decisions with git history for accurate changelog generation.

When should I run the changelog generator during a development sprint?▼

Run the generator during release cycles to ensure all commits, sprint outcomes, and design changes are captured and aligned by version. This timing produces both internal technical summaries and customer-facing release notes for the release.

Related Skills

Explore More Software Engineering Skills→
Ronin15Ronin15
14

hammer-changelog-generator

Generate a structured Markdown changelog from SDL3 HammerEngine git history.

Community
Intermediate
fagemxfagemx
58

game-docs

Generate player-facing patch notes and internal changelogs from git tags and commits.

Community
Advanced
bitwardenbitwarden
129

retrospecting

Generate structured retrospective reports from Claude Code session data.

Official
Intermediate
hadenlabshadenlabs
1

git-release

Parse git logs, categorize commits, and draft release notes with version bumps.

Official
Intermediate