hotfix

Guide production incident hotfixes with minimal specs and mandatory follow-up specifications.

Updated Feb 5, 2026
One-click install
npx skills add https://github.com/javierhbr/agnostic-agent-loop --skill hotfix-javierhbr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hotfix
Source: https://github.com/javierhbr/agnostic-agent-loop/tree/main/internal/skills/packs/sdd/hotfix
Command: npx skills add https://github.com/javierhbr/agnostic-agent-loop --skill hotfix-javierhbr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured, yet rapid, path for addressing urgent production issues and critical bugs, ensuring speed without sacrificing essential traceability and governance.

Core Features & Use Cases

  • Triage and Routing: Guides decisions on whether a fix requires a component-only or contract-changing approach.
  • Minimal Spec Creation: Enables fast creation of lightweight "Bug" or "Hotfix" specifications for urgent issues.
  • Guided Implementation & Verification: Provides steps for applying the fix and confirming its success.
  • Mandatory Follow-up: Enforces the creation of a comprehensive follow-up specification to address root causes, add tests, and document decisions.
  • Use Case: A critical payment processing bug is discovered in production. This Skill helps you quickly create a Hotfix Spec, implement the minimal change to restore service, validate the fix, and then ensures a follow-up spec is created to add proper tests and address the underlying issue.

Quick Start

Use the hotfix skill to guide a production incident response.

Frequently Asked Questions about hotfix

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

FAQPage Schema
How do I ensure production incident response fixes remain traceable without slowing down deployment?▼

A hotfix process enables rapid production incident resolution by creating lightweight Bug or Hotfix specifications for urgent issues. This ensures speed without sacrificing essential traceability and governance during critical bug resolution.

What is the best way to manage a critical production bug that changes system contracts?▼

Managing a contract-changing critical production bug requires triage and routing to determine the fix approach. You must apply minimal changes to restore service and then enforce a mandatory follow-up specification to address root causes and document decisions.

How do I create a minimal specification for an urgent production hotfix?▼

Creating a minimal specification for an urgent production hotfix involves generating lightweight Bug or Hotfix specs. This enables fast implementation of the minimal change needed to restore service while maintaining full traceability.

Do I need to create follow-up specifications after a component-only hotfix?▼

Yes, you must create mandatory follow-up specifications after a component-only hotfix. This enforces comprehensive documentation to address root causes, add proper tests, and facilitate system learning and hardening following the urgent fix.

When should I use a component-only fix instead of a contract-changing route for a critical bug?▼

You should use a component-only fix instead of a contract-changing route when the critical bug does not alter system interfaces. Triage and routing guide this decision based on whether the production incident requires modifying component internals or changing external contracts.