skills.rest
akiojin
akiojinCOMMUNITY
Explore all skills by this author →
Website𝕏@akiojinGitHub

hotfix

Create a hotfix branch, guide fixes, open a pull request to main, and confirm patch releases.

8|1|Updated Oct 30, 2025
Search Tags:#git#devops#github#release#branch#hotfix#pull-request
One-click install
npx skills add https://github.com/akiojin/llmlb --skill hotfix-akiojin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hotfix
Source: https://github.com/akiojin/llmlb/tree/main/.codex/skills/hotfix
Command: npx skills add https://github.com/akiojin/llmlb --skill hotfix-akiojin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines emergency production hotfix workflows by guiding maintainers through creating a hotfix branch from main, performing checks, opening a PR to main, and confirming patch releases to minimize downtime and mistakes.

Core Features & Use Cases

  • Preflight validation: Checks for a clean working tree, existence of main branch, and GitHub authentication before proceeding.
  • Branch and PR guidance: Creates a hotfix/* branch from main and provides step-by-step instructions for fixes, quality checks, pushing, and creating a pull request.
  • Release confirmation: Guides users to verify that a patch release is produced after merging.
  • Use Case: On detecting a production bug, use this flow to quickly create a hotfix branch, apply minimal changes with Conventional Commit messages, run quality checks, and open an auto-labeled PR for immediate review and release.

Quick Start

Create a hotfix branch from main for the reported issue, guide me through implementing the fix and quality checks, open the PR to main, and confirm the patch release.

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 from main for a production bug?▼

To create a hotfix branch from main, the workflow validates your clean working tree and GitHub authentication, generates a hotfix/* branch, and guides you through applying fixes, running checks, and opening a pull request to main.

What is the standard git hotfix workflow for patching a release?▼

A standard git hotfix workflow branches from main, applies minimal changes with Conventional Commit messages, runs quality checks, opens a PR, and confirms a patch release is produced after merging.

Do I need GitHub authentication to open a hotfix pull request?▼

Yes, successful GitHub authentication is required. The preflight validation checks for gh authentication and a clean working tree before proceeding with hotfix branch creation and pull request actions.

Can I use automation scripts to create a hotfix branch and PR?▼

Yes, the workflow supports optional scripts and release helpers to automate branch creation and pull request actions, streamlining the emergency hotfix process while guiding necessary checks.

What are the limitations of an emergency hotfix workflow?▼

This hotfix workflow requires a clean working tree, an existing main branch, and a GitHub-based PR and release workflow. It is not suitable for repositories lacking a main branch or unauthenticated gh access.

Related Skills

Explore More Software Engineering Skills→
pear-studiopear-studio
34

pr-create

Push a feature branch and generate a GitHub Pull Request from commit history.

Community
Intermediate
NVIDIANVIDIA
3.4k

release-cherry-pick

Cherry-pick labeled merged pull requests into release branches via GitHub CLI.

Official
Advanced
kk20300113-pngkk20300113-png

land-and-deploy

Merge pull requests and verify production health via canary checks.

Community
Advanced
taiga-Ktaiga-K
1

create-branch

Create GitFlow feature, release, and hotfix branches with validated naming.

Community
Intermediate