ship-web-games
Package, deploy, and verify a playable Three.js or web game. Use for release builds, asset delivery, private/public deployment, production smoke tests, browser proof, release notes, rollback readiness, and cleanup of temporary QA resources.
88%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Ship Web Games
Release only a verified commit and prove the deployed game, not merely the local build.
Release sequence
- Confirm the exact integration commit and preserve unrelated work.
- Run focused tests, lint/type checks, production build, and diff checks.
- Package and deploy the exact validated commit.
- Poll deployment status and open the production game in the repository-approved browser.
Production proof
Verify load, first input, one combat or core interaction, assets, save/settings if applicable, responsive view, console health, and representative performance. Report the deployed state separately from local readiness.
Finish cleanly
Record release evidence and rollback target. Close temporary dev servers, benchmarks, and QA tabs once no longer needed; do not terminate resources owned by another active task.
- Repository
MengTo/Skills
- Revision
7b5f032
- Last updated
- First committed
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.