hotfix

Automate emergency hotfix workflows with TDD and branch management.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/pdlc-os/pdlc --skill hotfix-pdlc-os
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hotfix
Source: https://github.com/pdlc-os/pdlc/tree/main/skills/hotfix
Command: npx skills add https://github.com/pdlc-os/pdlc --skill hotfix-pdlc-os

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Emergency hotfix workflows for production issues, enabling a compressed build–test–ship cycle while preserving guardrails and visibility.

Core Features & Use Cases

  • Pause an active feature during a production incident to stabilize the environment and prevent scope drift.
  • Sync with main, create a hotfix branch, and generate a Beads task to track incident ownership and metadata.
  • Enforce a focused Red–Green–Refactor TDD cycle to validate the fix before shipping.
  • Expedite shipping and lightweight verification to reduce mean time to recovery.
  • Automatically resume the paused feature after the hotfix completes, preserving state and context.

Quick Start

Provide a short hotfix slug and a one-line description of the issue to begin the hotfix workflow.

Frequently Asked Questions about hotfix

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

FAQPage Schema
How do I execute a rapid production hotfix without disrupting my active feature branch?

A production hotfix can be executed by automatically pausing your active feature, syncing with main, and branching a dedicated hotfix path to isolate the emergency fix while preserving your current development state.

What is the Red-Green-Refactor TDD cycle for shipping an emergency hotfix?

The Red-Green-Refactor TDD cycle enforces writing a failing test for the production issue, implementing the minimal code to pass it, and cleaning up the design before expediting the ship and verification steps.

How do I track ownership and metadata during a production incident hotfix?

Tracking incident ownership during a production hotfix involves generating a dedicated task item that records issue details, coordinates the branching strategy, and maintains visibility throughout the compressed build-test-ship cycle.

Does the hotfix workflow automatically resume paused feature development after recovery?

Yes, the hotfix workflow automatically resumes the paused feature development after completion, rebasing affected branches and updating state files to fully restore the original development context.

What's the best way to reduce mean time to recovery during a production incident?

Reducing mean time to recovery requires expediting shipping and lightweight verification steps, enforcing a focused TDD cycle to validate the fix, and automatically managing branch synchronization to stabilize the environment quickly.

When do I need to pause an active feature for a production hotfix?

You need to pause an active feature during a production incident to stabilize the environment, prevent scope drift, and safely sync with main before branching the hotfix to address the immediate issue.