How to use the Build Game Changelog agent skill

What does the skill make the agent do?

The skill tells the agent to treat the changelog as a release system. The core record is a single ledger of player-visible releases. A version identifies a successful production release, not a development commit, and the newest ledger entry defines the version shown throughout the game.

The agent also wires the screen into the game's menu state. Opening the changelog is a reversible menu transition, and the header toggle, visible X, bottom Back action, controller cancel, and Escape all route through one close function. It also checks layout on desktop and mobile.

• Reconstruct release history from deployments and Git, without inventing missing entries
• Define when a version number should change (one successful player-visible production deployment equals one version)
• Keep the displayed version synchronized with the live build
• Build responsive, accessible release-ledger UI with keyboard, controller and touch support

Install the skill: download the ZIP and unzip it

Download the ZIP for this skill from this page. Then install it in one of two ways.

For a personal install, unzip it into ~/.claude/skills/. To limit it to one game project, unzip it into that project's .claude/skills/ folder. Either way, the skill folder should contain SKILL.md, references/reference-architecture.md and agents/openai.yaml.

You can also upload the skill in the Claude apps under Settings → Capabilities → Skills.

• Personal: ~/.claude/skills/
• Project only: .claude/skills/ inside your game repository
• Claude apps: Settings → Capabilities → Skills, then upload

Trigger the skill with a natural request

You do not need a special command. Describe the task in plain language and mention the changelog or version screen. The skill's description covers requests to add or revise a changelog or version screen, reconstruct release history from deployments and Git, define version-bump rules, keep displayed versions synchronized with live builds, or test changelog mechanics across desktop and mobile.

Give the agent the context it needs: the game repository, the menu or pause system, and where your deployment history lives.

• "Add an in-game changelog screen to the pause menu, opened from the version number."
• "Backfill our changelog from the hosting provider's deployment history and our Git log."
• "Make sure the version shown in the game matches the live build."
• "Check that the changelog works with Escape, a controller and touch on mobile."

Set up what the skill needs

The skill assumes three things. Without them, it cannot do accurate work and the result would be thin or guessed.

Git repository access is needed to diff source revisions. Access to production deployment records, such as your hosting provider's deployment history, lets the agent verify which revisions players received. The game codebase must already have a menu or pause state machine and an input binding layer to hook into.

• Git repository access for the game project
• Production deployment records that show which revisions players received
• A game codebase with an existing menu or pause state machine and input bindings

Safety notes: scripts and network

This skill does not run scripts and does not use the network, according to its listing. It works by reading your repository and deployment records and then editing source files.

Because the agent will edit your game code and may publish builds, review its diff before committing, and confirm the deployment succeeded before treating a version as released. The skill itself says not to fabricate history or release dates; if evidence is incomplete, the agent should stop and ask.

• No scripts are run by the skill
• No network use is declared by the skill
• Review the proposed source changes before committing
• Check the live game after release, as the skill's release order requires

Tips for good results

Keep the version scheme you already use. For a new pre-1.0 game with no scheme, the skill defaults to 0.9.0 and increments the patch number once per production release. It does not jump to a new minor or major version without an explicit product milestone.

Write player-facing notes such as "Restore vitality at checkpoints" rather than "Various fixes." Keep commit hashes and deployment IDs in internal metadata, not in player copy.

• Keep your existing version scheme if you have one
• Do not bump the version for local commits, drafts or failed builds
• Combine commits shipped together into one version; give a separate hotfix its own version
• Ask the agent to run the data, accessibility and responsive checks it lists