skills.rest
easonlao
easonlaoCOMMUNITY
Explore all skills by this author →
GitHub

changelog

Generates coach-approvable and player-facing changelogs from Git history and Bugzilla data with LLM-assisted drafting.

Updated Apr 25, 2026
Search Tags:#changelog#versioning#release notes#design docs#documentation automation#git commits#sprint reports
One-click install
npx skills add https://github.com/easonlao/jiazi-game --skill changelog-easonlao
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: changelog
Source: https://github.com/easonlao/jiazi-game/tree/main/.claude/skills/changelog
Command: npx skills add https://github.com/easonlao/jiazi-game --skill changelog-easonlao

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes the manual, error-prone work of writing release notes by compiling changes from git history, sprint planning context, and design documents into clear internal and player-facing outputs.

Core Features & Use Cases

  • Version/Sprint-scoped changelog generation: Produce a changelog for a specific git tag or a sprint date range so releases stay accurate and timely.
  • Change categorization with traceability: Classify commits into features, improvements, fixes, balance changes, misc, and known issues while tracking commits that lack task references.
  • Two audience outputs: Create an internal technical changelog and a player-facing version with safe messaging that avoids internal code paths and developer details.

Quick Start

Run the changelog skill for the version you want, for example: “Generate the changelog for version v0.0.1”.

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?▼

You generate release notes by aggregating git commit history, sprint reports, and design documents for a specified version or sprint range, then categorizing and summarizing the changes into structured release notes.

Can I automatically categorize git commits into features, fixes, and improvements for documentation?▼

Yes, git commits can be automatically categorized into features, improvements, fixes, balance changes, misc, and known issues, while also tracking commits that lack task references for accurate documentation.

How do I create player-facing release notes that hide internal code paths and developer details?▼

You create player-facing release notes by generating a separate output version with safe messaging that avoids internal code paths and developer details, keeping it distinct from the internal technical changelog.

Do I need git tags to scope changelog generation for a specific software release?▼

Git tags are not strictly required; you can derive the relevant change window from either git tags or sprint dates to scope the changelog generation accurately for a specific software release.

How do I append generated changelogs to an existing docs/CHANGELOG.md file?▼

You append generated changelogs to an existing docs/CHANGELOG.md file by using append and overwrite controls, optionally writing the categorized results directly into your project documentation.

Related Skills

Explore More Product & Management Skills→
scomofoscomofo

changelog

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

Community
Advanced
FrancisVargaFrancisVarga

patch-notes

Generate player-facing patch notes from changelogs, git history, and QA records.

Community
Advanced
mikkeymoomikkeymoo
1

mm-release

Automate version bumping, changelog updates, tagging, and repository pushes.

Community
Advanced
nmdranmdra
26

keep-a-changelog

Parse Git commit history and format CHANGELOG.md entries per Keep a Changelog standards.

Community
Intermediate