hotfix

Coordinate emergency hotfix workflows with audit trails from triage to deployment.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/WindXRan/y3td --skill hotfix-windxran
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hotfix
Source: https://github.com/WindXRan/y3td/tree/main/.claude/skills/hotfix
Command: npx skills add https://github.com/WindXRan/y3td --skill hotfix-windxran

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a controlled emergency hotfix workflow so critical production bugs can be fixed quickly without losing accountability, approval history, or correct backporting.

Core Features & Use Cases

  • Severity-gated triage: Classifies issues into S1/S2/S3 and redirects S3-and-below into the normal bug-fix process to prevent unnecessary process overhead.
  • Hotfix record with audit trail: Creates a standardized hotfix record capturing problem, root cause, fix, testing, rollback plan, and required approvals.
  • Branch + deploy discipline: Creates a hotfix branch when in a git repo, gathers parallel sign-offs, runs an explicit QA re-entry gate, and then merges to both release and development branches.
  • Post-deploy verification + closure: Verifies the bug resolution in the deployed build and schedules a post-incident retrospective within 48 hours.

Quick Start

Run the hotfix workflow for your issue by issuing the command: /hotfix [bug-id or description].

Frequently Asked Questions about hotfix

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

FAQPage Schema
How do I manage an emergency hotfix workflow for a production incident?

An emergency hotfix workflow coordinates fixing production issues with a complete audit trail from triage to deployment. It enforces severity gating, records hotfix metadata to disk, performs optional git branching via Bash checks, and uses sign-off gates for QA entry.

When should I use a severity-gated triage process for urgent bug remediation?

Severity-gated triage for urgent bug remediation classifies issues into S1, S2, and S3 to prevent unnecessary process overhead. It redirects S3-and-below severity issues into the normal bug-fix process while reserving the full hotfix workflow for critical production bugs.

How do I create a hotfix branch and ensure correct backporting to release and development branches?

Creating a hotfix branch involves using Bash checks in a git repository, gathering parallel sign-offs, running a QA re-entry gate, and then merging the fix to both release and development branches to ensure correct backporting and maintain branch discipline.

What is included in a hotfix record audit trail for deployment verification?

A hotfix record audit trail captures the problem, root cause, fix, testing, rollback plan, and required approvals. It creates a standardized record that provides full traceability and accountability for emergency production deployments.

Can I use this hotfix process for S3 production bugs?

No, this hotfix process redirects S3-and-below bugs into the normal bug-fix process. Severity gating ensures only S1 and S2 urgent bug remediation scenarios proceed through the full emergency deployment workflow with scoped QA verification.

What happens after post-deploy verification in an incident management hotfix?

After post-deploy verification confirms bug resolution in the deployed build, the incident management hotfix workflow schedules a post-incident retrospective within 48 hours to review the emergency response and identify process improvements.