Agent-agnostic skills for game jams: app versioning, start/launcher scripts, release verification, and Godot UI verification
- Go Template 64.1%
- Python 35.9%
| Filename | Latest commit message | Latest commit date |
|---|---|---|
| docs | ||
| examples | ||
| skills | ||
| README.md | ||
game-jam-skills
A small, vendor-neutral set of agent skills and notes for game-jam and hobby projects (Godot-leaning,
but mostly generic). Each skill is a folder with a SKILL.md (YAML frontmatter with name and
description, then plain-Markdown instructions) that any coding agent can follow.
What's included
| Path | What it is |
|---|---|
skills/app-versioning/ |
Install/apply a two-phase versioning policy (pre-beta: every app-code commit bumps; beta: one bump per branch/tranche). |
skills/create-start-script/ |
Generator for cross-platform start.sh / start.ps1 launchers for Python apps (venv, deps, git self-update). It does not target Godot projects. |
skills/release-verify/ |
Checklist for confirming a release/CI run really produced the claimed end state. |
skills/verify-godot-ui/ |
Drive a real Godot 4 UI headlessly under Xvfb to verify gameplay/view changes. |
docs/versioning-standard.md |
The versioning standard (two variants) behind app-versioning. |
docs/godot-overlay.md |
Example Godot 4 / GDScript guidance to paste into your agent instructions. |
examples/godot-versioning-example.md |
Sample docs/VERSIONING.md for a hypothetical Godot game. |
Installing a skill
Copy the skill folder into whatever location your coding agent reads skills from, for example
.claude/skills/<name>/ or .cursor/... (project-local), or your agent's user-level skills directory.
For agents with no skill mechanism, point the agent at the SKILL.md ("follow
skills/release-verify/SKILL.md") or paste it into your instructions file (AGENTS.md etc.).
Keep each skill's references/ and scripts/ folders next to its SKILL.md.
Using each skill
- app-versioning — ask your agent to "adopt app-versioning" (or run
/app-versioningif your agent supports slash skills). It detects the phase, canonical version file, and app-code paths, then writes aVersioningblock into your agent instructions file anddocs/VERSIONING.md. Arguments:install,flip-beta,classify,pr-prep. - create-start-script — for a Python project: ask the agent to "create a start script". It writes
start-script.spec.json(seereferences/spec.md) and runspython3 skills/create-start-script/scripts/generate.py --spec start-script.spec.json --out .to emitstart.sh,start.ps1and a defaultstart.cfg. Self-update uses whatever git remote/upstream your checkout has. - release-verify — after a release or CI run, ask the agent to verify the end state against live forge state (release by tag, asset names, prerelease flag, body).
- verify-godot-ui — fill in the bindings table (probe dir, main scene, persistence flag, screen size, lint command), then have the agent write and run a probe under
xvfb-run.