Hotfix

Enforce diagnostic, implementation, and verification phases for production hotfixes.

6|3|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/carson-sweet/sweetclaude --skill hotfix-carson-sweet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Hotfix
Source: https://github.com/carson-sweet/sweetclaude/tree/main/skills/hotfix
Command: npx skills add https://github.com/carson-sweet/sweetclaude --skill hotfix-carson-sweet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured, disciplined workflow for applying urgent production patches while preventing scope creep and ensuring post-incident accountability.

Core Features & Use Cases

  • Strict Scope Enforcement: Ensures only the immediate fix is implemented, preventing accidental refactoring or unrelated changes during high-pressure situations.
  • Integrated TDD: Mandates a regression test to reproduce the failure before the fix is applied, ensuring the issue is truly resolved.
  • Post-Mortem Automation: Automatically generates a backlog item for a post-mortem to ensure root cause analysis and long-term prevention.

Quick Start

Invoke the hotfix skill to begin the diagnostic process for a critical production issue.

Frequently Asked Questions about Hotfix

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

FAQPage Schema
How do I apply a production hotfix without introducing unrelated changes?

A controlled production hotfix workflow enforces strict scope boundaries, ensuring you implement only the minimal patch required. This prevents accidental refactoring or unrelated code changes during high-pressure incident resolution.

Does fixing a critical production incident require a regression test first?

Yes, fixing a critical production incident should include a regression test first. A TDD approach mandates reproducing the failure before applying the patch, ensuring the high-priority defect is truly resolved and verified.

What's the best way to ensure a post-mortem happens after an urgent patch?

The best way to ensure a post-mortem happens is to automate its creation within the patch workflow. Generating a backlog item immediately after resolving the incident enforces root cause analysis and long-term prevention accountability.

Do I need git to execute a minimal-patch workflow for a software incident?

Yes, you need git to execute a minimal-patch workflow for a software incident. Version control is required to manage the expedited production patches and maintain system stability throughout the diagnostic and verification phases.

What phases are required when applying expedited production patches?

Applying expedited production patches requires diagnostic, implementation, and verification phases. This controlled workflow ensures immediate resolution of critical software defects without compromising system stability or documentation standards.