release

Runs verification gates and publishes versioned GitHub Releases for the Flix game engine.

5|Updated May 5, 2026
One-click install
npx skills add https://github.com/ababup1192/flix_game_engine --skill release-ababup1192
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/ababup1192/flix_game_engine/tree/main/.claude/skills/release
Command: npx skills add https://github.com/ababup1192/flix_game_engine --skill release-ababup1192

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Deciding how much testing to run during development and executing a safe, complete release of the Flix game engine is error-prone: full test suites are slow, generated assets are invisible to git, and precommit gates fail for recurring reasons. This Skill codifies the exact verification loop, byte-identical rendering comparison, and release checklist so nothing is skipped. ## Core Features & Use Cases - Scoped test loop: Run only make test-<name> for affected packages during development, reserving the full make test-par gate for release time. - Byte-identical render verification: Use make render-par, make reference-check, and per-template benchmarks to prove refactors did not change generated images, since gallery/ is untracked by git. - Release checklist: A copyable 5-step checklist covering make bump FROM=x TO=y, commit/push, make release, and external fetch validation, plus known failure modes of precommit, jargon, sync, and lint gates. - Use Case: After refactoring engine rendering code, follow the Skill to re-render all templates, confirm zero diffs in assets/sfx, then bump the version and cut a GitHub Release with the bundled engine zip. ## Quick Start Ask the AI to follow the release skill to verify the current changes and cut a new release with make bump and make release.

Frequently Asked Questions about release

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

FAQPage Schema
How do I release a new version of the Flix game engine?

Commit all engine sources, run make bump FROM=x TO=y, commit and push, then run make release. The release target runs sync, the full test-par gate, gl-parity, build-pkg, bundle-zip, and gh release create in one pass.

How do I verify a refactor did not change rendered output?

Run make render-par at the root, confirm git status shows zero diffs in assets/sfx, then run make -C each template bench to compare against reference SHAs. Images without references must be inspected visually in gallery/.

Should I run the full test suite during everyday development?

No. Run make test-<name> only for packages affected by your change and use flix check elsewhere. The full parallel gate make test-par runs once, right before release.

Why does make release stop before publishing?

make release aborts when engine sources have uncommitted changes. Note that gallery/ and NOTES.md are untracked and never block it. Commit every visible diff in git status before retrying.

Why does the precommit hook fail and how do I preview it?

Run bin/fge precommit --files <staged files> before committing to rehearse the gate. Common failures are a stale docs/api-digest.md, docs sync drift caught by make check-docs-sync, and jargon flagged by bin/fge jargon.

What does make test-par report zero tests?

A log that cuts off during dependency resolution with zero tests indicates parallel contention, not real failures. Re-run the affected package with make test-<name> alone, or fall back to sequential make test or make release TEST=test.