Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →donchitos/release-checklist
Generates a comprehensive pre-release validation checklist covering build verification, certification requirements, store metadata, and launch readiness.
Passed 9 of 15 test cases with the skill, and 5 of 15 without it.
and 5 more in the full report
8 fixed6 passed either way8 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
A newer attempt on gemini-3.8-flash on 10/19/2026 did not produce a publishable comparison (not comparable). The snapshot above is the previously measured run.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
In the Quality Gates section of the release checklist, what continuous runtime requirement is defined for the soak test?
| Checked | Without skill | With skill |
|---|---|---|
| Specifies a minimum 4-hour continuous play session requirement for passing the soak test. | Missed | Passed |
The instructions your model reads when the skill loads.
!bash "${CLAUDE_SKILL_DIR}/../../hooks/yaml-helper.sh" resolve_config --keys rigor,workflow,project.stage,cert_tier,automation
Automation mode: Resolve modes.automation (project.local.yaml →
project.yaml → default collaborative). Every AskUserQuestion call and
every file write follows .claude/docs/automation-modes.md
(collaborative asks always · guided major-only · autonomous logs and proceeds;
automation_always_ask categories always prompt).
Resolved above — use as-is. No block → defaults in .claude/docs/config-resolution.md.
Scope this checklist to the project. Emitting every item for every platform trains the reader to skip the list, which defeats the gate:
project.stage — items for phases this project has not reached are out of
scope; say so rather than listing them unchecked.
modes.rigor — at minimal, drop items whose only justification is process
weight this project has opted out of.
platform.cert_tier — emit certification items only for the tier the
project targets. If it is unset, ask which platforms are in scope
rather than emitting all of them — an unset value is a question, not a licence
to emit every certification track. If it cannot be determined, mark the section
NOT ASSESSED — cert tier unknown. Unset is not none: none is a
decision, unset is a missing one, and they must not produce the same output.
Branch on the four values this key takes — none | itch | steam | console —
and not on platform names. The full requirement table is the ## platform.cert_tier
section of .claude/docs/effects-map.md — read only that section (Grep its
heading, then a bounded Read); the file as a whole is not a runtime input.
none — emit no certification section at all. Internal release, alpha or
jam game. Say the section was omitted and why; do not leave it blank.itch — itch.io upload requirements only: build size, page setup, age tags.
No console and no Steamworks items.steam — Steamworks: store page, depot build, achievements, system
requirements, common content rules. No console certification items.console — full platform certification (TRC / XR / Lotcheck), save-data
rules, controller-mapping rules, age-rating boards. The heaviest tier.Branch on the
cert_tiervalues above, not on platform names. "Emit console/mobile certification items only for the platforms the project targets"
test cases passed, vs 5 / 15 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.