changelog

Provide a target version or sprint number, and the Skill reads git log since the last tag, categorizes each commit, and outputs a formatted internal changelog plus a player-facing version. It also cross-references sprint reports and design docs for context.

The Skill translates technical commits into player-friendly language, describing what players experience rather than code changes. It excludes internal file paths, developer names, and code references, and includes design reasoning for balance changes.

If no tags exist, the Skill falls back to reading the full git log or a reasonable recent range of about 100 commits. It verifies the directory is a git repository first and aborts gracefully with a message if git is unavailable.

Yes. 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.

No. It presents both changelogs first, then asks whether to append to or overwrite docs/CHANGELOG.md, or skip writing entirely. Appending is the recommended default when the file already exists.