changelog

Generate categorized internal and player-facing changelogs from git history and sprint reports.

Updated Jul 22, 2025
One-click install
npx skills add https://github.com/MichaelSolati/mkai --skill changelog-michaelsolati
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog
Source: https://github.com/MichaelSolati/mkai/tree/main/profiles/game-dev/skills/changelog
Command: npx skills add https://github.com/MichaelSolati/mkai --skill changelog-michaelsolati

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually compiling changelogs from scattered git commits, sprint reports, and design documents is time-consuming, error-prone, and often lacks the context needed for both internal teams and external players. This Skill automates the entire process, delivering accurate, categorized changelogs that save hours of manual work and ensure consistency across releases.

Core Features & Use Cases

  • Dual Output Generation: Creates both detailed internal changelogs with technical details (commit hashes, owners, affected systems) and polished, player-facing changelogs focused on user experience.
  • Context-Aware Categorization: Pulls data from git history, sprint plans, and design documents to automatically sort changes into categories like new features, bug fixes, balance changes, and known issues.
  • Metrics & Compliance Tracking: Automatically counts total commits, tracks lines changed, and flags commits missing task references for team visibility.
  • Use Case: A game development team can use this Skill to turn a month of git commits and sprint work into a ready-to-post player changelog and a detailed internal release document in seconds, no manual copy-pasting required.

Quick Start

Use the changelog skill to generate a full set of internal and player-facing changelogs for the latest release version.

Frequently Asked Questions about changelog

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

FAQPage Schema
How do I automatically generate changelogs from git commit history and sprint reports?

Automating changelog generation from git commit history and sprint reports pulls categorized release notes without manual data aggregation. This process extracts commits, tracks metrics, and flags missing task references to produce context-rich internal and player-facing documentation.

Can I generate separate internal and player-facing release notes from the same git history?

Generating separate internal and player-facing release notes from the same git history creates dual outputs. Internal logs include technical details like commit hashes and owners, while player-facing logs focus on user experience and polished summaries.

What is the best way to categorize game development balance changes and bug fixes in release notes?

Categorizing game development balance changes and bug fixes in release notes is best handled by context-aware automation. Pulling data from git history and design documents automatically sorts changes into categories like new features, bug fixes, and known issues.

Does automated changelog generation track commit metrics and lines changed?

Automated changelog generation tracks commit metrics and lines changed by counting total commits and flagging commits missing task references. This provides team visibility and ensures compliance tracking across the release documentation.

Do I need design documents to generate internal team-facing release notes?

Design documents are not strictly required but enhance internal team-facing release notes by providing design intent context. The automation pulls from git history, sprint plans, and design documents to deliver accurate, categorized changelogs with full context.