skills.rest
imgamer
imgamerCOMMUNITY
Explore all skills by this author →
GitHub

changelog

Generate internal and player-facing Markdown release notes from git commits and sprint reports.

Updated Dec 22, 2024
Search Tags:#git#changelog#release notes#sprint planning#design documentation#player communication#commit categorization
One-click install
npx skills add https://github.com/imgamer/AILearn --skill changelog-imgamer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: changelog
Source: https://github.com/imgamer/AILearn/tree/main/game-studios/Claude-Code-Game-Studios-e375f/.claude/skills/changelog
Command: npx skills add https://github.com/imgamer/AILearn --skill changelog-imgamer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the manual effort of writing release notes by automatically turning recent git activity, sprint reports, and design documents into clear changelogs.

Core Features & Use Cases

  • Auto-changelog generation: Produces both an internal engineering changelog and a player-facing changelog from commit history and supporting docs.
  • Sprint- and version-aware scope: Uses a git tag when a version is provided, or derives a sprint date range when a sprint number is provided.
  • Change categorization: Classifies commits into features, improvements, bug fixes, balance changes, known issues, and miscellaneous items, while tracking commits that lack task/story references.

Quick Start

Use the changelog skill to create a new release entry for version by running a single command like: "Generate the changelog for version 1.4.0".

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 automatically?▼

You can generate release notes by providing a version number or sprint identifier, which prompts the Skill to analyze your git commit range and output categorized internal and player-facing Markdown changelogs.

How do I create player-facing changelogs from internal engineering commits?▼

This Skill correlates git commits with sprint reports and design documents to categorize changes, generating both internal engineering changelogs and player-ready release notes in Markdown format.

Does this changelog generator work with sprint-based update cycles instead of git tags?▼

When a sprint number is provided instead of a version tag, the tool derives a sprint date range to analyze commits, making it suitable for sprint-based update cycles alongside version-tagged releases.

Can I categorize git commits into features, bug fixes, and balance changes for release notes?▼

The Skill classifies commits into features, improvements, bug fixes, balance changes, known issues, and miscellaneous categories, while tracking commits that lack task or story references during changelog generation.

Do I need git installed to generate changelogs from commit history?▼

Yes, git availability is required because the Skill performs git availability checks and analyzes commit ranges directly from your repository history to generate the changelog content.

What happens to git commits that lack task references during changelog generation?▼

Commits lacking task or story references are tracked and grouped into a miscellaneous items category, ensuring unlinked git activity is documented in the internal engineering changelog for review.

Related Skills

Explore More Product & Management Skills→
scomofoscomofo

changelog

Generate categorized release notes from git history for internal and player audiences.

Community
Advanced
plurigridplurigrid
60

changelog-generator

Generate user-facing changelogs from git commit history.

Official
Advanced
nuoyanruoshuinuoyanruoshui
47

changelog

Generate structured internal and player-facing changelogs from git commits and project documentation.

Community
Advanced
DonchitosDonchitos
23.7k

changelog

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

Community
Advanced