skills.rest
frabcd
frabcdCOMMUNITY
Explore all skills by this author →
GitHub

changelog

Generates internal and player-facing changelogs from git commits, sprint reports, and design documents.

13|Updated Jul 30, 2026
Search Tags:#git#changelog#game development#versioning#documentation#release notes#sprint
One-click install
npx skills add https://github.com/frabcd/codex-ai-game-studio --skill changelog-frabcd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: changelog
Source: https://github.com/frabcd/codex-ai-game-studio/tree/main/plugins/ai-game-studio/skills/changelog
Command: npx skills add https://github.com/frabcd/codex-ai-game-studio --skill changelog-frabcd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing release changelogs by hand means digging through git history, sprint reports, and design docs, then rewriting everything twice—once for the team and once for players. This Skill automates that entire process. ## Core Features & Use Cases - Dual Changelog Generation: Produces a technical internal changelog with commit hashes, owners, and metrics, plus a player-facing version free of jargon and internal references. - Automatic Categorization: Classifies commits into new features, improvements, bug fixes, balance changes, and known issues, and flags commits lacking task references. - Controlled File Output: Asks for confirmation before appending to or overwriting docs/CHANGELOG.md. - Use Case: After finishing sprint 12, run the Skill with the sprint number to get a categorized internal changelog with metrics and a ready-to-post player-facing summary. ## Quick Start Use the changelog skill to generate internal and player-facing changelogs for version 1.4 from the git history since the last tag.

Frequently Asked Questions about changelog

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

FAQPage Schema
How do I generate a changelog from git commits automatically?▼

Provide a version tag or sprint number and the Skill reads git log since the last tag, categorizes each commit into features, fixes, and balance changes, then outputs formatted internal and player-facing changelogs.

How to write player-facing release notes from technical commits?▼

The Skill rewrites technical commit messages into player-friendly language that describes the experience rather than the implementation, and strips out code references, file paths, and developer names.

Does changelog generation work without git tags?▼

Yes. If no tags exist, the Skill falls back to reading the full git log or the last 100 commits. It aborts gracefully with a message if the directory is not a git repository at all.

Can I append a new changelog entry to an existing CHANGELOG.md?▼

Yes. After generating the changelogs, the Skill asks whether to append the entry to the top of docs/CHANGELOG.md, overwrite the file, or skip writing entirely. Appending is the recommended default when the file exists.

What happens with vague or uncategorizable commit messages?▼

Unclear commits are placed in a Miscellaneous category, and the Skill checks associated files and sprint data for context. It also counts commits lacking task references and reports that number in the metrics section.

Related Skills

Explore More Product & Management Skills→
dnkrowdnkrow
1

changelog

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

Community
Advanced
dawn840705dawn840705

patch-notes

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

Community
Intermediate
striderZAstriderZA
72

changelog

Generate categorized changelogs from git commits, sprint reports, and design documents.

Community
Intermediate
TriNgo0108TriNgo0108

changelog-automation

missing_configuration

Community
Intermediate