day-one-patch
FeaturedPrepare a day-one patch for a game launch. Scopes, prioritises, implements, and QA-gates a focused patch addressing known issues discovered after gold master but before or immediately after public launch. Treats the patch as a mini-sprint with its own QA gate and rollback plan.
Install
Quality Score: 97/100
Skill Content
Details
- Author
- Donchitos
- Repository
- Donchitos/Claude-Code-Game-Studios
- Created
- 9 months ago
- Last Updated
- 1 weeks ago
- Language
- Shell
- License
- MIT
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
patch
Cut a patch release (X.Y.Z to X.Y.Z+1) of the current git repo, committed as "vX.Y.Z - Summary", tagged, and pushed.
preflight
Release-readiness gate — one orchestrated pass before code ships: full test suite + lint/typecheck, dependency & security quick pass, docs drift, config/migration/flag check, changelog draft from commits, and a GO / GO-WITH-RISKS / NO-GO verdict with a suggested deploy command (never executed). TRIGGER when: the user is about to ship/release/deploy/tag ("are we ready to ship", "preflight", "release check", "can this go out"). TRIGGER ALSO on the same ask phrased as plain work, with this skill unnamed — "anything blocking release", "run the pre-release checks", "is main safe to deploy" — an ask for a ship/no-ship judgment IS this skill. DO NOT TRIGGER when: the user wants a review of one diff (use /code-review), a security-only sweep (use /audit-security), or to settle an epic's plans and archives (use /close-epic — run it before this when an epic is involved).
ce-patch
Make one low-risk change on a bounded lane that touches at most two candidate files, proves it with behavior red→green or a deterministic content/config before→after check, and ends at one human acceptance gate. Any uncertain, sensitive, dependency, durable-state, schema, public-contract, destructive, colliding, or wider change routes to /core-engineering:ce-plan; this skill never commits, pushes, opens a PR, or merges. Triggers: a typo, localized bug fix, or small behavior change with a known test. Multi-file, contract, schema, dependency, security-sensitive, or exploratory work → /core-engineering:ce-plan.