speckit-hotfix

Automate emergency hotfix workflow with branch generation and incident logging.

Updated Mar 13, 2026
One-click install
npx skills add https://github.com/refactory-lang/refactory-template --skill speckit-hotfix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-hotfix
Source: https://github.com/refactory-lang/refactory-template/tree/main/.claude/skills/speckit-hotfix
Command: npx skills add https://github.com/refactory-lang/refactory-template --skill speckit-hotfix

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides an expedited workflow for creating emergency hotfixes, bypassing standard procedures for critical issues while ensuring a mandatory post-mortem analysis.

Core Features & Use Cases

  • Emergency Hotfix Creation: Quickly initiate a hotfix process for urgent production issues.
  • Expedited Workflow: Bypasses normal TDD and allows for test-after deployment in critical situations.
  • Mandatory Post-Mortem: Schedules a post-mortem to analyze the incident and prevent recurrence.
  • Use Case: A critical bug is causing a service outage. Use this Skill to immediately create a hotfix branch, log the incident, and prepare for rapid deployment, followed by a scheduled post-mortem.

Quick Start

Initiate an emergency hotfix by running the command /speckit.workflows.hotfix with a description of the incident.

Frequently Asked Questions about speckit-hotfix

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

FAQPage Schema
How do I create an emergency hotfix for a critical production issue?

An emergency hotfix workflow automates hotfix branch generation, incident log creation, and reporting next steps for expedited deployment to resolve critical production issues immediately.

What is the best way to ensure a post-mortem happens after an expedited deployment?

A mandatory post-mortem analysis schedules a review to analyze the incident and prevent recurrence, ensuring accountability after bypassing standard TDD procedures for critical production issues.

How do I bypass TDD for an urgent production issue?

You bypass TDD for urgent production issues by initiating an expedited hotfix workflow that allows test-after deployment, prioritizing immediate service restoration over standard test-first procedures in critical situations.

Do I need a spec-kit project structure to run the hotfix workflow?

Yes, the hotfix workflow requires a spec-kit project structure containing a .specify/ directory and specific workflow extensions to automate hotfix ID, branch generation, and incident logging successfully.

What steps are involved in an expedited hotfix workflow?

The expedited hotfix workflow steps include executing scripts for hotfix ID and branch generation, creating an incident log, reporting next steps for expedited deployment, and scheduling a mandatory post-mortem to analyze the incident.

When should I not use an expedited hotfix workflow?

Avoid using the expedited hotfix workflow for non-critical production issues because it bypasses standard TDD and normal procedures, designed exclusively for critical situations requiring immediate attention and mandatory post-mortem analysis.