changelog

Generate internal and external changelogs from git history and sprint reports.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/sumilee-pcu/game2026 --skill changelog-sumilee-pcu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog
Source: https://github.com/sumilee-pcu/game2026/tree/main/.claude/skills/changelog
Command: npx skills add https://github.com/sumilee-pcu/game2026 --skill changelog-sumilee-pcu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the manual overhead of tracking changes across git commits, sprint reports, and design documents, ensuring consistent and professional release documentation.

Core Features & Use Cases

  • Dual-Format Generation: Creates both detailed internal technical logs and polished, player-facing release notes.
  • Contextual Synthesis: Automatically aggregates data from git history, sprint reports, and design documents to provide meaningful context for changes.
  • Use Case: Use this at the end of a sprint to instantly generate a clean, categorized changelog for your Steam community page while maintaining a detailed technical record for your development team.

Quick Start

Use the changelog skill to generate release notes for the current sprint or version.

Frequently Asked Questions about changelog

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

FAQPage Schema
How do I automate release notes generation from git commit history and sprint data?

Automated release notes generation synthesizes git commits, sprint reports, and design documents to produce categorized changelogs. This process eliminates manual tracking overhead by automatically aggregating technical updates into distinct feature, bug fix, and balance change buckets.

What is the best way to create dual-format changelogs for internal teams and external players?

Dual-format changelog generation creates both detailed internal technical logs and polished external release notes. By analyzing git history and sprint reports, it translates raw technical updates into categorized narratives suitable for community pages while maintaining comprehensive development records.

Can I generate categorized changelogs that separate feature updates from bug fixes automatically?

Categorized changelog generation automatically sorts technical updates into feature, bug fix, and balance change buckets. By analyzing commit history and sprint reports, the system parses raw development data to classify changes into structured release narratives without manual sorting.

Do I need git integration and project management directory access to synthesize release narratives?

Git integration and project management directory access are required to synthesize accurate release narratives. The changelog generation process pulls contextual data from commit history, sprint reports, and design documents to aggregate meaningful context for technical and external documentation.

When should I use an automated changelog generator instead of manually tracking sprint changes?

Automated changelog generation is ideal at the end of a sprint to instantly produce clean, categorized release notes. Manual tracking introduces overhead and inconsistency, whereas synthesizing git commits and sprint reports ensures professional, comprehensive documentation for both internal and external use.

What limitations exist when synthesizing release documentation from git history and design documents?

Release documentation synthesis requires accessible git history and project management directories to function accurately. Limitations arise if sprint reports or design documents are incomplete, preventing the system from generating meaningful context or categorizing technical updates into structured changelog narratives.