Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →donchitos/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.
Passed 18 of 24 test cases with the skill, and 10 of 24 without it.
and 5 more in the full report
8 fixed10 passed either way6 still failing0 broke1 errored
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
A user reported a minor visual glitch where a shadow flickers during the sunset cycle in level 3. What standard bug reporting command should be used to log this issue for future backlog grooming?
| Checked | Without skill | With skill |
|---|---|---|
| Recommends logging the visual bug via standard bug reporting tools instead of starting a hotfix. | Missed | Passed |
The instructions your model reads when the skill loads.
Explicit invocation only: This skill should only run when the user explicitly requests it with
/hotfix. Do not auto-invoke based on context matching.
Read the bug description or ID. Assess severity on /bug-triage's scale:
Confirm with AskUserQuestion:
[A] S1 (Critical) — crash, data loss, or complete feature failure[B] S2 (High) — major feature broken, game still playable[C] S3 or lower — redirect to normal bug fix workflowIf [C]: stop. Verdict: REDIRECTED — use the normal bug fix workflow for S3 and below.
Draft the hotfix record:
## Hotfix: [Short Description]
Date: [Date]
Severity: [S1/S2]
Reporter: [Who found it]
Status: IN PROGRESS
### Problem
[Clear description of what is broken and the player impact]
### Root Cause
[To be filled during investigation]
test cases passed, vs 10 / 24 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.