Menu

Individual skill

workflow-ship-change

0upvotes

Ship every change the way the user requires, with the guardrails. Take screenshots of the start, the key moment and the result; give the change its own changelog version with pictures; verify with tests; commit only your own files; merge with the latest main and push as a fast-forward; publish that exact main live; confirm each step; and report measured sizes, asking before any upload over 50 MB. Use at the end of every change (feature, fix, tweak, art, balance, polish) and whenever the user says "ship it", "commit", "push", "merge", "publish", "deploy", "go live" or "update the changelog". Project specifics (hosting, the changelog pipeline, merge conflicts) go in an optional local references/<project>.md next to this skill.

agent-skills/workflow/workflow-ship-change/SKILL.md

Read pinned source

Source commit 5ea1661a0e05d82b054553daaa6baf6d0233c33c

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
7,346
Repository last updated
Nov 8, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# 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.
Back to top