changelog

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

Updated Feb 8, 2024
One-click install
npx skills add https://github.com/kay6198835/Game-RPG --skill changelog-kay6198835
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog
Source: https://github.com/kay6198835/Game-RPG/tree/main/.claude/skills/changelog
Command: npx skills add https://github.com/kay6198835/Game-RPG --skill changelog-kay6198835

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Changelog generation across git commits, sprint reports, and design documents is automated to save time and reduce manual errors.

Core Features & Use Cases

  • Automated aggregation of commits since the last release or tag, sprint notes, and design docs into a single changelog.
  • Dual-output formats for internal teams and end users (player-facing) to keep stakeholders aligned.
  • Configurable targets via version or sprint number to tailor the changelog scope.

Quick Start

Run the changelog skill with a target version or sprint number to generate both internal and player-facing changelogs.

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 can run the changelog skill with a target version or sprint number. It reads git history, sprint reports, and design documents to populate sections in the changelog automatically.

Can I create separate release notes for internal teams and end users?

Yes, automated changelog generation supports dual-output formats for internal teams and end users. This keeps internal stakeholders and external audiences aligned with appropriately scoped release notes.

Does this changelog generator work with design documents and sprint reports?

Yes, the changelog generator aggregates data from design documents and sprint reports alongside git commits. This provides a comprehensive view of release changes beyond code-level updates.

What is the best way to scope changelog generation for a specific release?

The best way to scope changelog generation is by configuring targets via version or sprint number. This tailors the changelog scope to specific releases, ensuring only relevant commits and documents are included.

Why use an automated changelog tool instead of manually compiling release notes?

Automated changelog generation saves time and reduces manual errors by aggregating commits, sprint notes, and design docs. This ensures consistent, comprehensive documentation across release planning and sprint reviews.