workflow-ship-change

Installation
SKILL.md

Workflow: ship a change

A change is done only when all of these are true, and the report shows each one:

  1. Screenshots of the real rendered game: the start state, the key moment and the result. They're shown inline in the report.
  2. Its own changelog version, with its pictures on the in-game changelog page.
  3. Verified:
    • your own tests;
    • the tests of commits you merged in;
    • the asset checks;
    • the full suite, run on the pushed commit.
  4. Committed: one cohesive commit, with only your own files staged.
  5. Pushed to main as a fast-forward, and confirmed on GitHub.
  6. Live: the build of that exact main is published, and confirmed working on the real domain.
  7. Measured: the sizes of the commit, the push, any upload and the publish, all measured, never estimated.

Pushing and publishing are standing authorizations for the project's own repository and live site. So don't ask before them, except where a guardrail below says stop. Read the project's AGENTS.md before starting, and this skill's references/<project>.md if there is one. Project rules change often, and wherever they differ from this skill, they win.

Guardrails: stop and ask the user

Installs
255
Repository
mengto/skills
GitHub Stars
6.9K
First Seen
Sep 28, 2026