skills.rest
MengTo
MengToCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

build-game-changelog

Implements versioned in-game changelog screens with release ledgers and menu navigation.

5.7k|685|Updated Feb 3, 2026
Search Tags:#release management#Deployment#Versioning# accessibility#Game development#ChangeLog#menu navigation
One-click install
npx skills add https://github.com/MengTo/Skills --skill build-game-changelog
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: build-game-changelog
Source: https://github.com/MengTo/Skills/tree/main/agent-skills/game-development/build-game-changelog
Command: npx skills add https://github.com/MengTo/Skills --skill build-game-changelog

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Game changelogs often become decorative modals with invented version numbers, broken close behavior, and release notes that disagree with what actually shipped. This Skill turns the changelog into a release system tied to real production deployments, with one authoritative ledger, correct menu-state navigation, and verified live-version behavior.

Core Features & Use Cases

  • Release Ledger Design: Builds a typed, schema-validated changelog data source with contiguous versions, deployment provenance, and a derived current version.
  • History Backfilling: Reconstructs release history from production deployments, source revisions, and Git diffs without fabricating dates or features.
  • Menu & Accessibility Integration: Implements toggle, close, Back, controller cancel, and Escape through one back action with proper focus management and responsive layout.
  • Use Case: A game has shipped five deployments but shows a hard-coded version string. Use this Skill to backfill a 0.9.0–0.9.4 ledger from deployment records, wire the changelog into the pause menu, and verify the live build displays the correct version.

Quick Start

Use the build-game-changelog skill to add a versioned changelog screen to my game that reflects our actual production releases.

Frequently Asked Questions about build-game-changelog

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

FAQPage Schema
How do I add a changelog screen to my game?▼

Add the changelog as an explicit menu screen or route, not a floating modal. Record the previous screen before opening, route the toggle, X, Back, and Escape through one close function, and render releases newest-first from a structured ledger.

How do I backfill a game changelog from deployment history?▼

Enumerate successful production deployments, map each to its source revision and date, diff consecutive revisions, and summarize player-visible changes. Work oldest-to-newest, store entries newest-first, and never invent missing dates or features.

What versioning scheme should a pre-1.0 game changelog use?▼

Default to 0.9.0 for the first production baseline and increment the patch once per successful production release: 0.9.1, 0.9.2, and so on. Do not bump for local commits, drafts, or failed builds, and keep one version per deployed release.

Why does my game version badge disagree with the changelog?▼

This happens when the version is maintained as a separate hand-written constant. Derive the displayed current version from the newest ledger entry so the UI badge, package metadata, and ledger cannot drift apart.

How do I handle Escape and controller cancel in a game menu?▼

Resolve cancel intent once through the game's input-binding layer, respecting higher-priority consumers like dialogs, drag operations, and rebinding flows. Avoid registering a separate global Escape listener, which can close two layers at once.

Can a changelog entry reference its own commit hash?▼

No, a commit cannot contain its own final hash. Keep the newest entry's source revision pending and backfill it during the next release, inject the revision at build time, or store provenance in an external release manifest.

Related Skills

Explore More Software Engineering Skills→
ZateZate
9

worklog-management

Maintain a markdown worklog with commit references for completed tasks.

Community
Intermediate
VetCodersVetCoders
1

vc-release

Coordinate production releases by tagging commits, generating changelogs, and publishing artifacts.

Official
Advanced
nguyenpv1980-wqnguyenpv1980-wq
2

risk-tiered-validation-selector

Classify changed files into docs-only, fast, or full validation tiers.

Community
Advanced
OpusGameLabsOpusGameLabs
307

game-deploy

Deploy browser games to static hosting via automated build and publish steps.

Official
Advanced