hf-hotfix

Analyzes root cause and prepares a handoff to hf-test-driven-dev.

1|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/hujianbest/garage-agent --skill hf-hotfix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hf-hotfix
Source: https://github.com/hujianbest/garage-agent/tree/main/packs/coding/skills/hf-hotfix
Command: npx skills add https://github.com/hujianbest/garage-agent --skill hf-hotfix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides engineering teams through urgent production defect analysis, root-cause convergence, and the definition of a minimal, safe repair boundary, enabling precise handoff to the next stage in the hotfix workflow.

Core Features & Use Cases

  • Root Cause Analysis (RCA) and 5 Whys to identify the true cause rather than symptoms
  • Minimal Safe Fix Boundary definition to prevent scope creep
  • Structured handoff preparation to hf-test-driven-dev with evidence, scope, and gates

Quick Start

Follow reproduction steps, converge root cause, define the minimal safe repair boundary, and prepare for handoff

Frequently Asked Questions about hf-hotfix

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

FAQPage Schema
How do I perform root cause analysis for a production hotfix?

Root cause analysis for a production hotfix uses structured methods like RCA and 5 Whys to identify the true cause rather than symptoms. This ensures you converge on the actual defect mechanism instead of applying superficial patches.

What is a minimal safe repair boundary in hotfix workflows?

A minimal safe repair boundary defines the exact scope of code changes needed to fix a defect without introducing scope creep. It prevents unnecessary modifications during urgent hotfix situations, keeping the deployment safe and targeted.

How do I prepare a structured handoff after reproducing a defect?

To prepare a structured handoff after reproducing a defect, document the evidence, scope, and gate requirements. This ensures the next phase of the hotfix workflow receives verified context for implementing the actual code repair.

Can I use 5 Whys to prevent scope creep during urgent software engineering fixes?

Yes, using 5 Whys helps prevent scope creep by forcing convergence on the true root cause. Once identified, you define a minimal safe repair boundary that strictly limits changes to what is necessary for the urgent fix.

Do I need to reproduce an issue before defining the repair boundary?

Yes, you need to reproduce the issue first to verify the defect exists and gather evidence. Reproduction is a required step before converging on the root cause and defining the minimal safe repair boundary for the hotfix.