changelog

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

3|Updated Jun 3, 2026
One-click install
npx skills add https://github.com/Negentropy-Laby/Constitution-Driven-Development --skill changelog-negentropy-laby
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog
Source: https://github.com/Negentropy-Laby/Constitution-Driven-Development/tree/main/.agents/skills/changelog
Command: npx skills add https://github.com/Negentropy-Laby/Constitution-Driven-Development --skill changelog-negentropy-laby

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically generate a structured internal changelog from git commits, sprint notes, and design documents to keep teams aligned.

Core Features & Use Cases

  • Auto-generates an internal changelog by aggregating git commits, sprint reports, and design documents.
  • Categorizes changes by feature, bug, task, and sprint, presenting a versioned changelog for cross-team visibility.
  • Use case: produce an internal changelog for a release cycle covering Game and Product domains.

Quick Start

Run the changelog tool with a version tag to generate the internal changelog for that release.

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 from git commits, run the changelog tool with a version tag. It parses git logs, sprint reports, and design documents to categorize changes and assemble a structured changelog for that release cycle.

Can I categorize git commits by feature, bug, and sprint for an internal changelog?

Yes, you can categorize git commits by feature, bug, task, and sprint. The tool aggregates commits, sprint reports, and design documents to categorize changes and present a versioned internal changelog for cross-team visibility.

Does the changelog tool work with design documents and CDD docs?

Yes, the changelog tool works with design and CDD docs. It applies to software projects with design documents and sprint workflows, parsing these alongside git logs to produce versioned records for Game and Product domains.

What is the best way to keep Game and Product teams aligned on release changes?

The best way to keep teams aligned is generating a structured internal changelog. Aggregating git commits, sprint notes, and design documents produces a versioned changelog that provides cross-team visibility across Game and Product domains.

How do I create a versioned changelog for a specific release cycle?

You create a versioned changelog by running the tool with a release version tag. It automates parsing git logs, sprint reports, and design documents to assemble the structured changelog for that specific release cycle.