changelog

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

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/nevesb/idol-agency-maker --skill changelog-nevesb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog
Source: https://github.com/nevesb/idol-agency-maker/tree/main/.claude/skills/changelog
Command: npx skills add https://github.com/nevesb/idol-agency-maker --skill changelog-nevesb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of clear, consistent changelogs by aggregating git commits, sprint reports, and design documents so release notes no longer require tedious manual summarization.

Core Features & Use Cases

  • Aggregate Change Data: Read git history and tags, ingest sprint reports from production/sprints, and consult design documents in design/gdd to gather context for changes.
  • Categorization and Metrics: Classify commits into New Features, Improvements, Bug Fixes, Balance Changes, Known Issues, and Miscellaneous; compute counts, files changed, and commits without task references.
  • Dual Output and Safe Write: Produce a detailed internal changelog and a polished player-facing changelog, then optionally append or overwrite docs/CHANGELOG.md after confirming with the user.
  • Use Case: A release manager or product lead preparing a version or sprint summary can quickly generate both technical and player-facing notes from repository history.

Quick Start

Generate a changelog for the target version or sprint and offer to append it to docs/CHANGELOG.md.

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?

Generate release notes by parsing git history and tags, analyzing sprint reports and design documents, categorizing changes, and computing metrics before writing to docs/CHANGELOG.md.

How do I categorize git commits into features and bug fixes for a changelog?

Categorize git commits into New Features, Improvements, Bug Fixes, Balance Changes, Known Issues, and Miscellaneous by analyzing commit history alongside sprint reports and design documents.

Can I create both internal technical changelogs and player-facing release notes for game development?

Create dual output for game development by generating a detailed internal technical changelog and a polished player-facing changelog from the same repository history and design documents.

What is the best way to aggregate git history and design documents for version summaries?

Aggregate git history and design documents for version summaries by reading git tags, ingesting production sprint reports, and consulting game design documents to gather contextual change data.

Does generating a changelog overwrite existing docs/CHANGELOG.md files?

Generating a changelog does not automatically overwrite docs/CHANGELOG.md; it offers to safely append or overwrite the file only after receiving explicit user confirmation.

What metrics are calculated when generating changelogs from git history?

When generating changelogs from git history, metrics calculated include change counts per category, total files changed, and the number of commits lacking explicit task references.