day-one-patch

Prepare 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.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/day-one-patch/SKILL.md

Quality

Content

92%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is a well-structured, highly actionable mini-sprint workflow with strong sequencing and validation gates. The only notable gap is progressive disclosure: large templated sections could be externalized into reference files.

Suggestions

Move the patch-record markdown template (Phase 6) and the bug-classification table into reference files (e.g. references/patch-record-template.md) and link to them one level deep to reduce inline bulk.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes competence, using terse bullets, tables, and exact file paths without explaining concepts Claude already knows, so every token earns its place.	3 / 3
Actionability	It gives concrete, executable guidance: exact production file paths, AskUserQuestion prompts with literal option strings, specific slash-command invocations, and named agent Task spawns, leaving no ambiguity about what to do.	3 / 3
Workflow Clarity	The seven phases are clearly sequenced with explicit validation checkpoints ('Do not proceed to Phase 4 until the rollback plan is written', 'QA verdict must be PASS or PASS WITH WARNINGS') and feedback loops for FAIL recovery.	3 / 3
Progressive Disclosure	No bundle files exist and the ~227-line body is well-organized into sections, but substantial content like the full patch-record template and classification tables is inline rather than split into one-level-deep references.	2 / 3
	Total	11 / 12 Passed

Description

67%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific and well-differentiated, clearly scoping a distinct game-launch patch workflow. Its main weakness is the absence of an explicit 'Use when...' trigger clause and reliance on technical jargon over natural user phrasing.

Suggestions

Add an explicit 'Use when...' trigger clause naming natural user phrases, e.g. 'Use when preparing a day-one or launch patch for a shipped game, or when cert feedback requires post-submission fixes.'

Soften jargon ('gold master', 'QA-gates') or pair each term with a plain-language equivalent so the description reads like something a user would actually say.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions in third person ('Scopes, prioritises, implements, and QA-gates a focused patch'), matching the anchor for listing several specific concrete actions.	3 / 3
Completeness	It clearly answers 'what' but the 'when' is framed as a temporal window ('after gold master but before or immediately after public launch') rather than an explicit 'Use when...' trigger clause, which per the judging guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	It includes some natural user terms like 'day-one patch' and 'game launch' but leans heavily on technical jargon ('gold master', 'QA-gates') and misses common phrasings a user might actually say, so it does not reach full natural-term coverage.	2 / 3
Distinctiveness Conflict Risk	The day-one launch-patch niche is highly specific with distinct triggers ('day-one patch', 'gold master', 'game launch'), making conflict with other skills unlikely.	3 / 3
	Total	10 / 12 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: Donchitos/Claude-Code-Game-Studios
Path: .claude/skills/day-one-patch/SKILL.md
Commit: 984023d

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.