skills.rest
onemanking
onemankingCOMMUNITY
Explore all skills by this author →
GitHub

hotfix

Creates emergency hotfix branches with audit records, approvals, and rollback plans.

Updated Apr 13, 2026
Search Tags:#release management#incident response#hotfix#bug triage#git branch#rollback plan#emergency fix
One-click install
npx skills add https://github.com/onemanking/the-operator --skill hotfix-onemanking
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hotfix
Source: https://github.com/onemanking/the-operator/tree/main/.github/skills/hotfix
Command: npx skills add https://github.com/onemanking/the-operator --skill hotfix-onemanking

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Critical production bugs cannot wait for the normal sprint cycle, but rushing a fix without process creates untracked changes and regressions. This Skill provides a structured emergency workflow that fixes the issue fast while preserving a full audit trail. ## Core Features & Use Cases - Severity Triage: Classifies bugs as S1 (critical) or S2 (major) and redirects lower-severity issues to the normal bug fix workflow. - Documented Hotfix Records: Creates a hotfix record in production/hotfixes/ capturing problem, root cause, fix, testing, approvals, and rollback plan. - Approval Workflow: Collects sign-off from lead-programmer, qa-tester, and producer subagents before deployment. - Use Case: A game-breaking crash is reported on the release build. Invoke the hotfix workflow to create a hotfix branch from the release tag, implement the minimal fix, document the root cause, and route approvals before merging back to both release and development branches. ## Quick Start Run /hotfix with a bug ID or description, such as asking to hotfix the save-file corruption crash reported in issue 142.

Frequently Asked Questions about hotfix

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create an emergency hotfix for a production bug?▼

Invoke the hotfix workflow with a bug ID or description. It assesses severity, creates a hotfix record in production/hotfixes/, branches from the release tag, implements the minimal fix, and collects approvals before deployment.

What severity levels qualify for a hotfix workflow?▼

Only S1 (critical: game unplayable, data loss, security vulnerability) and S2 (major: significant feature broken with workaround) qualify. S3 or lower severity issues are redirected to the normal bug fix workflow.

Does a hotfix branch merge back into the development branch?▼

Yes, hotfix branches merge to both the release branch and the development branch. This ensures the fix is not lost when future development continues from the main development line.

When should I not use the hotfix workflow?▼

Avoid it for low-severity bugs that can wait for the normal sprint cycle, and for fixes requiring more than 4 hours of work. Complex fixes should be escalated to the technical-director for a scope decision instead.

What approvals are required before deploying a hotfix?▼

Three approvals are required: the lead-programmer reviews fix correctness and side effects, the qa-tester runs targeted regression tests, and the producer approves deployment timing and communication.

Related Skills

Explore More Software Engineering Skills→
clawpod-appclawpod-app
46

bug-report

Generate structured bug reports with reproduction steps and severity assessments.

Community
Intermediate
johnatas-henriquejohnatas-henrique

hotfix

Coordinate emergency bug fixes with approvals, QA gating, and backporting.

Community
Advanced
yersonargotevyersonargotev
1

tdd

Writes a failing regression test before fixing a bug with a clear test path.

Community
Intermediate
LeKayLeKay

hotfix

Create a hotfix branch, track approvals, and backport fixes.

Community
Advanced