hotfix

Triage production hotfixes and diagnose root cause from repository and CI context.

2|Updated Jan 22, 2026
One-click install
npx skills add https://github.com/abnegate/claudes --skill hotfix-abnegate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hotfix
Source: https://github.com/abnegate/claudes/tree/main/skills/hotfix
Command: npx skills add https://github.com/abnegate/claudes --skill hotfix-abnegate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Emergency production issues often require a rapid, low-risk fix with confidence that tests and CI will pass before shipping.

Core Features & Use Cases

  • Triage and context gathering: Assesses severity and gathers git state, recent deploys, and recent CI failures in parallel to pinpoint the likely fault.
  • Minimal-change hotfix execution: Creates a dated hotfix branch, reproduces and diagnoses in parallel, then implements the smallest viable fix.
  • Regression-proof delivery: Adds exactly one targeted regression test, runs the full test suite, performs a focused review, and iterates until everything passes before opening the PR and providing rollback-aware deployment guidance.

Quick Start

Use the hotfix workflow to fix a production bug by asking for an emergency response with the issue description as input, then follow the generated plan through PR creation and deployment steps.

Frequently Asked Questions about hotfix

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

FAQPage Schema
How do I handle a production incident with a minimal git hotfix?

Handling a production hotfix involves triaging severity, diagnosing the root cause from CI and git context, applying the smallest fix, adding one regression test, and opening a PR with rollback guidance.

What is the best way to plan a rollback for a production hotfix?

Rollback planning for a hotfix involves generating safe PR-based deployment instructions that include rollback-aware steps, ensuring you can revert the minimal change if it fails in production.

Does this hotfix workflow require running the full test suite before opening a GitHub pull request?

Yes, the hotfix workflow enforces a full test suite pass and performs a focused review, iterating until everything passes before opening the GitHub pull request to ensure regression-proof delivery.

Can I use this for CI troubleshooting when recent deployments fail?

Yes, you can use this for CI troubleshooting because it gathers recent CI failures and recent deploys in parallel to pinpoint the likely fault before applying a targeted fix.

When should I not use a minimal change approach for a production incident?

You should avoid using a minimal change hotfix for production incidents requiring broad architectural changes, as this workflow specifically targets critical issues needing the smallest viable fix and exactly one regression test.