skills.rest
nuoyanruoshui
nuoyanruoshuiCOMMUNITY
Explore all skills by this author →
GitHub

changelog

Generate structured internal and player-facing changelogs from git commits and project documentation.

47|12|Updated Jun 14, 2026
Search Tags:#changelog#release notes#git history#patch notes#sprint reports#change categorization
One-click install
npx skills add https://github.com/nuoyanruoshui/GodotGameFramework --skill changelog-nuoyanruoshui
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: changelog
Source: https://github.com/nuoyanruoshui/GodotGameFramework/tree/main/Godot/.claude/skills/changelog
Command: npx skills add https://github.com/nuoyanruoshui/GodotGameFramework --skill changelog-nuoyanruoshui

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill transforms scattered git commits, sprint reports, and design documents into structured release notes, reducing the effort required to explain technical changes and player-visible improvements.

Core Features & Use Cases

  • Change Aggregation: Collects release data from git history, sprint reports, and completed design documents.
  • Audience-Specific Writing: Produces both an internal changelog with technical ownership and metrics and a player-facing version focused on user impact.
  • Change Classification: Organizes work into features, improvements, bug fixes, balance changes, known issues, and miscellaneous updates.
  • Use Case: Use it at the end of a sprint or before a release to turn recent repository activity into reviewed internal documentation and community-ready patch notes.

Quick Start

Use the changelog skill with a version number or sprint number to generate internal and player-facing release notes from the relevant project history.

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

Generate release notes by aggregating git commits, sprint data, and design documents to produce structured internal changelogs and player-facing patch notes. The workflow categorizes changes into features, improvements, bug fixes, and balance changes.

Can I create player-facing patch notes separately from internal technical changelogs?▼

Yes, you can create separate player-facing patch notes and internal changelogs from the same repository activity. Internal versions include technical ownership and metrics, while player-facing versions focus on user impact and visible improvements.

What is the best way to categorize git commits into features, bug fixes, and improvements?▼

Categorize git commits by applying change classification to repository history, organizing work into features, improvements, bug fixes, balance changes, known issues, and miscellaneous updates for accurate release records.

How do I turn recent repository activity into reviewed internal documentation before a release?▼

Turn repository activity into internal documentation by running the changelog workflow with a version or sprint number, aggregating task-reference metrics and design documents to produce reviewed release records.

Does this changelog workflow require specific commit message formats or sprint tracking tools?▼

No specific commit message formats or external sprint tracking tools are required. The workflow aggregates data from repository history, sprint data, and completed design documents to generate accurate release records.

When should I use automated change categorization for sprint reviews instead of manual summaries?▼

Use automated change categorization for sprint reviews when you need to transform scattered git commits and design documents into structured release notes, reducing manual effort to explain technical changes and improvements.

Related Skills

Explore More Software Engineering Skills→
johnlindquistjohnlindquist
24

changelog

Generate changelogs from git commits and history as release notes.

Community
Basic
plurigridplurigrid
60

changelog-generator

Generate user-facing changelogs from git commit history.

Official
Advanced
scomofoscomofo

changelog

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

Community
Advanced
nuoyanruoshuinuoyanruoshui
47

patch-notes

Transform technical release changelogs into player-facing patch notes.

Community
Advanced