### Hotfix
Works with
description: "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."
argument-hint: "[bug-id or description]"
allowed-tools: Read, Glob, Grep, Write, Edit, Bash, Task
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionhotfixExecute the skills CLI command in your project's root directory to begin installation:
Fetches hotfix from Donchitos/Claude-Code-Game-Studios and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate hotfix. Access via /hotfix in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
10.7K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
10.7K
stars
| name | hotfix |
| description | "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." |
| argument-hint | "[bug-id or description]" |
| user-invocable | true |
| allowed-tools | Read, Glob, Grep, Write, Edit, Bash, Task |
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. Determine severity:
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]
### Fix
[To be filled during implementation]
### Testing
[What was tested and how]
### Approvals
- [ ] Fix reviewed by lead-programmer
- [ ] Regression test passed (qa-tester)
- [ ] Release approved (producer)
### Rollback Plan
[How to revert if the fix causes new issues]
Ask: "May I write this to production/hotfixes/hotfix-[date]-[short-name].md?"
If yes, write the file, creating the directory if needed.
If git is initialized, create the hotfix branch:
git checkout -b hotfix/[short-name] [release-tag-or-main]
Focus on the minimal change that resolves the issue. Do NOT refactor, clean up, or add features alongside the hotfix.
Validate the fix by running targeted tests for the affected system. Check for regressions in adjacent systems.
Update the hotfix record with root cause, fix details, and test results.
Use the Task tool to request sign-off in parallel:
subagent_type: lead-programmer — Review the fix for correctness and side effectssubagent_type: qa-tester — Run targeted regression tests on the affected systemsubagent_type: producer — Approve deployment timing and communication planAll three must return APPROVE before proceeding. If any returns CONCERNS or REJECT, do not deploy — surface the issue and resolve it first.
After approvals, determine the QA scope required before deploying the hotfix. Spawn qa-lead via Task with:
Ask qa-lead: Is a full smoke check sufficient, or does this fix require a targeted team-qa pass?
Apply the verdict:
/smoke-check against the hotfix build. If PASS, proceed to Phase 6./team-qa [affected-system] scoped to the changed system only. If QA returns APPROVED or APPROVED WITH CONDITIONS, proceed to Phase 6./team-qa sprint. This delays deployment but prevents a bad patch.Do not skip this gate. A hotfix that breaks something else is worse than the original bug.
Update the original bug file if one exists:
## Fix Record
**Fixed in**: hotfix/[branch-name] — [commit hash or description]
**Fixed date**: [date]
**Status**: Fixed — Pending Verification
Set **Status**: Fixed — Pending Verification in the bug file header.
Output a deployment summary:
## Hotfix Ready to Deploy: [short-name]
**Severity**: [S1/S2]
**Root cause**: [one line]
**Fix**: [one line]
**QA gate**: [Smoke check PASS / Team-QA APPROVED]
**Approvals**: lead-programmer ✓ / qa-tester ✓ / producer ✓
**Rollback plan**: [from Phase 2 record]
Merge to: release branch AND development branch
Next: /bug-report verify [BUG-ID] after deploy to confirm resolution
technical-directorAfter deploying, run /bug-report verify [BUG-ID] to confirm the fix resolved the issue in the deployed build.
If VERIFIED FIXED: run /bug-report close [BUG-ID] to formally close it.
If STILL PRESENT: the hotfix failed — immediately re-open, assess rollback, and escalate.
Schedule a post-incident review within 48 hours using /retrospective hotfix.
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
JuliusBrussee/caveman
JuliusBrussee/caveman
whyashthakker/agent-skills-marketing
JuliusBrussee/caveman
whyashthakker/agent-skills-marketing
vercel-labs/skills
Solid pick for teams standardizing on skills: hotfix is focused, and the summary matches what you get after install.
hotfix has been reliable in day-to-day use. Documentation quality is above average for community skills.
I recommend hotfix for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
hotfix has been reliable in day-to-day use. Documentation quality is above average for community skills.
Solid pick for teams standardizing on skills: hotfix is focused, and the summary matches what you get after install.
Useful defaults in hotfix — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
We added hotfix from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
hotfix reduced setup friction for our internal harness; good balance of opinion and flexibility.
Registry listing for hotfix matched our evaluation — installs cleanly and behaves as described in the markdown.
hotfix has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 53