changelog

Generate changelogs from git history and design docs for Roblox projects.

8|Updated Apr 16, 2026
One-click install
npx skills add https://github.com/CodePhobiia/claude-roblox-game-studio --skill changelog-codephobiia
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog
Source: https://github.com/CodePhobiia/claude-roblox-game-studio/tree/main/.claude/skills/changelog
Command: npx skills add https://github.com/CodePhobiia/claude-roblox-game-studio --skill changelog-codephobiia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate a consistent, automatically produced changelog by analyzing git history and updated design/docs, reducing manual toil and ensuring release notes accuracy for Roblox projects.

Core Features & Use Cases

  • Automatically categorize commits by type (feat, fix, chore, docs, refactor) and group them into a cohesive changelog.
  • Cross-reference design documentation changes to link feature work with design updates, ensuring traceability.
  • Produce both technical changelog entries for engineering teams and a player-facing patch notes draft for releases.

Quick Start

Invoke the changelog skill to generate an unreleased changelog by analyzing git history since the last tag and cross-referencing updated design docs.

Frequently Asked Questions about changelog

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

FAQPage Schema
How do I automate changelog generation from git history for Roblox projects?

You can cross-reference design documentation changes with git history to link feature work directly to design updates, ensuring traceability. This integration maintains accuracy between technical changelog entries and updated project design docs for engineering teams.

Can I generate player-facing patch notes separately from internal engineering changelogs?

You can generate an unreleased changelog by analyzing git history since the last tag and cross-referencing updated design docs. Invoking the skill automates this workflow to produce patch notes drafts suitable for internal documentation across feature and bugfix workflows.

Does this changelog automation work with conventional commit types?

Roblox game projects with frequent commits and design updates are the primary target for this changelog automation. It standardizes release notes across feature, bugfix, and maintenance workflows by analyzing ongoing git history and design doc changes.

Why should I cross-reference design docs with git history for release notes?

Cross-referencing design docs with git history ensures traceability by linking feature work directly to design updates. This reduces manual toil and guarantees release notes accuracy by verifying documented changes against actual repository commits.