Game Post-Release Tasks

Game post-release automation handles verification, documentation updates, and Git tagging in one workflow. This Skill automates AILANG module compilation checks, updates CHANGELOG.md and release notes, archives design documents, and creates version tags—eliminating manual steps and reducing launch errors.

Yes. This automation validates that all sim/*.ail modules compile via ailang, run core entry functions, and the game builds and tests successfully. It catches compilation failures before release, ensuring only verified code reaches production.

Post-release automation consolidates documentation tasks: moving design docs from planned/ to implemented/, updating CLAUDE.md, creating release notes, and maintaining CHANGELOG.md. It keeps all records synchronized with the released version without manual file shuffling.

The automation compiles feedback collected during development, surfaces blocking issues for the AILANG team, and includes them in release documentation. This ensures feedback is captured and visibility is shared without post-release discovery gaps.

The Skill uses Git, ailang, make, and gh as dependencies but wraps them in scripts and validation steps. Basic familiarity with versioning and command-line tools helps, but the automation handles the orchestration—you provide the version number and trigger the workflow.

The automation includes validation steps that halt on compilation or test failures, preventing a broken release. Errors surface immediately so you can fix issues before the version tag is published and documentation is finalized.