changelog

Aggregate git commits, sprint reports, and design documents into changelogs.

Updated Aug 27, 2026

Search Tags:#automation #git #changelog #documentation #sprint #release-notes #design-docs

Ready to run

npx skills add https://github.com/naxoruto/TE-limonchero-3d --skill changelog-naxoruto

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: changelog
Source: https://github.com/naxoruto/TE-limonchero-3d/tree/main/.claude/skills/changelog
Command: npx skills add https://github.com/naxoruto/TE-limonchero-3d --skill changelog-naxoruto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automating changelog creation by aggregating git commits, sprint reports, and design documents into a clear, publishable record.

Core Features & Use Cases

Consolidates commit messages, sprint summaries, and design documents into a single changelog for internal teams.
Produces both internal release notes and player-facing versions to communicate changes effectively.
Supports targetting by version or sprint to generate focused, episode-specific changelogs.

Quick Start

Use this skill to generate a changelog for the current sprint or a specific version.

Frequently Asked Questions about changelog

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

FAQPage Schema

How do I auto-generate a changelog from git commits and sprint data?▼

To auto-generate a changelog, you aggregate git commits, sprint reports, and design documents into a comprehensive record. This process requires access to repository history and sprint data sources to produce both internal release notes and player-facing versions.

What's the best way to consolidate design documents and commit messages into release notes?▼

The best way to consolidate design documents and commit messages into release notes is by aggregating all software project artifacts. This produces internal release notes for development teams alongside player-facing versions to communicate changes effectively.

Can I create both internal release notes and player-facing changelogs from the same sprint data?▼

Yes, you can create both internal release notes and player-facing changelogs from the same sprint data. The aggregation process takes git commits and design documents to communicate software changes effectively to both internal teams and players.

Why generate changelogs by aggregating multiple design docs and sprint reports?▼

Generating changelogs by aggregating design docs and sprint reports solves the problem of manual documentation. It consolidates multiple software project artifacts into a single, clear, publishable record, ensuring comprehensive internal and player-facing release notes.