do-hotfix

Automates urgent production bug-fix branches from latest release tag with quality gates.

4|1|Updated Dec 30, 2025
One-click install
npx skills add https://github.com/lushly-dev/afd --skill do-hotfix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: do-hotfix
Source: https://github.com/lushly-dev/afd/tree/main/.claude/skills/do-hotfix
Command: npx skills add https://github.com/lushly-dev/afd --skill do-hotfix

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the process of addressing urgent bugs in production by creating a dedicated hotfix branch, implementing a minimal fix, verifying its correctness, and fast-tracking it through the commit and pull request process.

Core Features & Use Cases

  • Rapid Bug Resolution: Quickly create and deploy fixes for critical production issues.
  • Enforced Scope Discipline: Ensures hotfixes are strictly limited to the bug fix, preventing scope creep.
  • Automated Workflow: Delegates commit and PR creation to other skills for a seamless, fast-tracked process.
  • Use Case: A critical authentication bug is reported in production. This Skill is used to immediately create a hotfix branch, apply the fix, run quality gates, and create a PR to merge the fix back into the main branch.

Quick Start

Use the do-hotfix skill to create a hotfix for the authentication crash.

Frequently Asked Questions about do-hotfix

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

FAQPage Schema
How do I create a git hotfix branch for an urgent production issue?

To create a git hotfix branch for an urgent production issue, use do-hotfix to automatically branch from the latest release tag and enforce a minimal fix scope. It then verifies the fix with quality gates and delegates pull request creation.

What is the best way to automate emergency bug fixes in production?

Automating emergency bug fixes in production is best handled by do-hotfix, which streamlines the process by creating a dedicated branch, enforcing a strict bug-only scope, and fast-tracking the commit and pull request workflow.

Can I use do-hotfix for regular feature development instead of just bug fixes?

No, do-hotfix is not intended for regular feature development. It enforces strict scope discipline to ensure hotfixes are strictly limited to the urgent bug fix, preventing any scope creep during the emergency workflow.

How does do-hotfix ensure an emergency fix does not break existing functionality?

Do-hotfix ensures emergency fixes do not break existing functionality by verifying the applied fix with automated quality gates before delegating the commit and pull request creation for fast-tracking back into the main branch.

Do I need a specific git workflow setup to use do-hotfix for production hotfixes?

To use do-hotfix for production hotfixes, your git workflow must utilize release tags. The Skill automatically branches from the latest release tag to isolate the urgent bug fix and maintain production stability.