skills.rest
Zeyad-37
Zeyad-37COMMUNITY
Explore all skills by this author →
GitHub

hotfix

Coordinates emergency production fixes from release-tag branching through expedited review, deployment, and post-mortem.

Updated Apr 21, 2026
Search Tags:#deployment#post-mortem#git worktree#hotfix#emergency fix#production incident#release tag
One-click install
npx skills add https://github.com/Zeyad-37/tech-agency --skill hotfix-zeyad-37
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hotfix
Source: https://github.com/Zeyad-37/tech-agency/tree/main/.claude/skills/hotfix
Command: npx skills add https://github.com/Zeyad-37/tech-agency --skill hotfix-zeyad-37

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a critical bug hits production, teams need a fast, disciplined path from diagnosis to deployment without bypassing code review, testing, or version control hygiene. This Skill orchestrates the entire emergency response so nothing gets skipped under pressure. ## Core Features & Use Cases - Release-Tag Branching: Creates an isolated git worktree branched from the production release tag, ensuring unreleased work on main never leaks into the hotfix. - Expedited Review Pipeline: Runs parallel code review, conditional security review, and focused regression testing under a 1-hour SLA. - Full Lifecycle Coverage: Handles approval, production deployment with monitoring, merge-back to main via PR, and post-mortem documentation. - Use Case: A P0 crash spike appears in Crashlytics for the iOS app on v1.2.0. Invoke this Skill to cut hotfix/v1.2.1/fix-login-crash from the v1.2.0 tag, assign the minimal fix, get expedited review, deploy, and file the post-mortem. ## Quick Start Trigger the hotfix process by saying production is broken and describing the critical bug, affected version, and severity.

Frequently Asked Questions about hotfix

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

FAQPage Schema
How do I create a hotfix branch for a production bug in git?▼

Create a git worktree branched from the production release tag, not from main, using the naming convention hotfix/{version}/{short-description}. This isolates the fix and prevents unreleased work on main from reaching production.

What is the correct hotfix workflow for a critical production incident?▼

Assess severity and affected version, branch from the release tag in a worktree, implement the minimal backward-compatible fix, run parallel expedited review and focused regression tests, deploy after approval, then merge back to main via PR and write a post-mortem.

Should a hotfix branch from main or from a release tag?▼

Branch from the release tag currently in production, never from main. Branching from main risks shipping unreleased features alongside the emergency fix.

When is a security review required for a hotfix?▼

A security review is required only when the fix touches auth, encryption, PII handling, or dependencies. Otherwise it is skipped to keep the expedited review within the 1-hour SLA.

Why merge a hotfix back to main after deploying?▼

Merging back via PR ensures the next release does not regress the fix. Direct merges into main are avoided because they bypass required checks; the PR notes the fix is already live in production.

Related Skills

Explore More Software Engineering Skills→
Vincri126Vincri126

error-triage

Classify Sentry production errors by severity and root cause.

Community
Advanced
fabioc-alohafabioc-aloha

Root Cause Analysis Skill

Apply the 5 Whys methodology to identify root causes of problems.

Community
Advanced
pckienuitpckienuit

systematic-debugging

Diagnose complex software bugs through reproduction, isolation, and root cause analysis.

Community
Intermediate
andershi666andershi666
1

version-release

Automate minor and patch releases with branch creation, PRs, and GitHub Releases.

Community
Advanced