hotfix

Emergency fix workflow that bypasses normal sprint processes with a full audit trail. Creates hotfix branch, tracks approvals, and ensures the fix is backported correctly.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

100%

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

The skill body is concise, highly actionable, and sequences a risky hotfix workflow with explicit validation gates and feedback loops, while remaining self-contained and well-organized.

Dimension	Reasoning	Score
Conciseness	The body is lean and procedural with no concept explanations Claude already knows; every phase and template earns its place, matching the score-3 anchor.	3 / 3
Actionability	Concrete git commands, exact AskUserQuestion prompts and options, named Task subagent types, file paths, and copy-paste templates provide fully executable guidance.	3 / 3
Workflow Clarity	A clear 7-phase sequence carries explicit validation checkpoints and feedback loops (severity gate, three-approval gate, QA re-entry gate, post-deploy verify with rollback/escalate) for a risky operation.	3 / 3
Progressive Disclosure	A single well-organized file with clear phase sections needs no external references, and cross-skill handoffs (/smoke-check, /team-qa, /bug-report) are signaled rather than nested, satisfying the simple-skill allowance for score 3.	3 / 3
	Total	12 / 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 distinctive, naming concrete actions and a clear niche, but it lacks an explicit "Use when..." trigger and natural keyword coverage, capping completeness and trigger-term quality at 2.

Suggestions

Add an explicit trigger clause such as "Use when the user requests an emergency/hotfix fix that cannot wait for the normal sprint cycle."

Broaden natural trigger terms (e.g., "hotfix", "emergency patch", "urgent production fix", "backport") so users' phrasings match the skill.

Dimension	Reasoning	Score
Specificity	"Creates hotfix branch, tracks approvals, and ensures the fix is backported correctly" lists multiple specific concrete actions, matching the score-3 anchor rather than the single-domain score-2 example.	3 / 3
Completeness	The description answers "what" clearly but contains no "Use when..." trigger, and the rubric caps completeness at 2 when explicit trigger guidance is missing.	2 / 3
Trigger Term Quality	"Emergency fix" and "hotfix branch" are relevant keywords, but common user variations and a natural trigger clause are missing, so it sits at score 2 rather than the broad coverage of score 3.	2 / 3
Distinctiveness Conflict Risk	"Emergency fix workflow that bypasses normal sprint processes" with "hotfix", "audit trail", and "backport" defines a clear niche unlikely to trigger general bug-fix skills.	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/hotfix/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.