Orchestrate emergency hotfix workflows with approvals, QA verification, and rollback planning.
npx skills add https://github.com/dnkrow/skill --skill hotfix-dnkrow
Please help me install this Agent Skill. Skill: hotfix Source: https://github.com/dnkrow/skill/tree/main/claude-global/hotfix Command: npx skills add https://github.com/dnkrow/skill --skill hotfix-dnkrow
This Skill streamlines an emergency hotfix workflow so critical bugs can be fixed quickly while preserving traceability, approvals, QA gating, and safe deployment practices.
Use the hotfix skill to coordinate an S1 or S2 emergency fix end-to-end by invoking it explicitly as /hotfix with a bug ID or a short bug description.
High-intent search queries and answers about installing and using this skill.
An emergency hotfix workflow for critical production issues requires severity triage, structured record creation for audit traceability, and controlled deployment. It distinguishes S1/S2 incidents from lower priorities and mandates approvals from lead-programmer, qa-tester, and producer roles before proceeding.
To coordinate approvals and QA verification for urgent bug remediation, enforce severity-based gating that requires explicit sign-offs from lead-programmer, qa-tester, and producer. After approvals, run smoke checks or scoped team QA based on required coverage before controlled deployment.
You need a rollback plan for incident management during any emergency hotfix deployment. A controlled deployment process mandates rollback planning alongside minimal-risk implementation, ensuring you can safely revert changes if post-deploy bug verification fails or the production issue remains unresolved.
No, normal software workflows are not recommended for S1 and S2 incident resolution. Severity triage explicitly distinguishes these critical incidents from lower-priority issues, recommending the normal workflow only for S3 or lower while requiring dedicated hotfix branching and approval gating for emergencies.
To create a hotfix branch for production fixes, initiate an emergency process that ensures minimal code changes and merges to both release and development branches. This controlled branching strategy maintains codebase integrity while enabling rapid, auditable bug remediation.
After deploying a hotfix, post-deploy verification checks the fix against the bug. If the critical bug remains unresolved, the incident management process re-opens the issue and schedules a post-incident review to analyze the failure and improve future hotfix workflows.
tranhieuttRun an emergency hotfix process with branch creation, audit logging, and approvals.
FrancisVargaCoordinate emergency Git-based hotfixes with severity checks and QA approval gates.
zach-sourceImplement GitFlow branching with feature, release, and hotfix workflows.
packetalienCoordinate emergency hotfix workflows with staged approvals, testing, and deployment gating.
