hotfix

Execute the hotfix workflow when the user asks `hotfix` or `/hotfix`: create a hotfix branch from main, guide fix+checks, open PR to main, and confirm patch release.

5 stars

byakiojin

View on GitHub Installation ↓

Best use case

hotfix is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Execute the hotfix workflow when the user asks `hotfix` or `/hotfix`: create a hotfix branch from main, guide fix+checks, open PR to main, and confirm patch release.

Teams using hotfix should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

You only need a quick one-off answer and do not need a reusable workflow.
You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/hotfix/SKILL.md --create-dirs "https://raw.githubusercontent.com/akiojin/llmlb/main/.codex/skills/hotfix/SKILL.md"

Manual Installation

Download SKILL.md from GitHub
Place it in .claude/skills/hotfix/SKILL.md inside your project
Restart your AI agent — it will auto-discover the skill

How hotfix Compares

Feature / Agent	hotfix	Standard Approach
Platform Support	Not specified	Limited / Varies
Context Awareness	High	Baseline
Installation Complexity	Unknown	N/A

Frequently Asked Questions

What does this skill do?

Execute the hotfix workflow when the user asks `hotfix` or `/hotfix`: create a hotfix branch from main, guide fix+checks, open PR to main, and confirm patch release.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Hotfix Workflow

本番障害向けのホットフィックスフローを開始し、`hotfix/*` ブランチ作成からパッチリリース確認までを案内する。

## Preflight

- `git status --short` が空であること
- `main` ブランチが存在すること
- `gh auth status` が成功すること

## 実行内容

1. 前提条件チェック
2. `main` から `hotfix/*` ブランチ作成
3. 修正・品質チェック・PR作成・リリース確認の手順提示

## 使用方法

### パターンA: Issue番号を指定

```bash
./scripts/release/create-hotfix.sh 42
# -> hotfix/42
```

### パターンB: 説明を指定

```bash
./scripts/release/create-hotfix.sh fix-critical-bug
# -> hotfix/fix-critical-bug
```

### パターンC: 対話式

```bash
./scripts/release/create-hotfix.sh
```

## 修正後の流れ

```bash
# 1) 修正実装
git add .
git commit -m "fix: 緊急修正の説明"

# 2) 品質チェック
make quality-checks

# 3) プッシュ + PR
git push -u origin hotfix/xxx
gh pr create --base main --head hotfix/xxx \
  --title "fix: 緊急修正の説明" \
  --label "hotfix,auto-merge"

# 4) リリース確認
gh release view
```

## 注意

- 緊急修正以外の変更を含めない
- Conventional Commits で `fix:` プレフィックスを使う
- main マージ後はパッチ版（例: v1.2.4）が自動作成される

Related Skills

gwt-spec-to-issue-migration

from akiojin/llmlb

Migrate legacy spec sources to artifact-first GitHub Issue specs. Supports local `specs/SPEC-*` directories and body-canonical `gwt-spec` Issues using the bundled migration script.

gwt-pty-communication

from akiojin/llmlb

PTY based communication tools for Project Mode orchestration (Lead/Coordinator/Developer).

gwt-pr

from akiojin/llmlb

Create or update GitHub Pull Requests with the gh CLI, including deciding whether to create a new PR or only push based on existing PR merge status. Use when the user asks to open/create/edit a PR, generate a PR body/template, or says 'open a PR/create a PR/gh pr'. Defaults: base=develop, head=current branch (same-branch only; never create/switch branches).

gwt-pr-check

from akiojin/llmlb

Check GitHub PR status with the gh CLI, including unmerged PR detection and post-merge new-commit detection for the current branch.

gwt-fix-pr

from akiojin/llmlb

Inspect GitHub PR for CI failures, merge conflicts, update-branch requirements, reviewer comments, change requests, and unresolved review threads. Create fix plans and implement after user approval. Reply to ALL reviewer comments with action taken or reason for not addressing, then resolve threads. Notify reviewers after fixes.

release

from akiojin/llmlb

Execute the release workflow when the user asks `release` or `/release`: sync develop, update version/changelog, create `chore(release)` commit, collect closing issues, create develop->main release PR, and verify release/publish artifacts.

drawio

from akiojin/llmlb

Create and edit draw.io diagrams in XML format. Use when the user wants to create flowcharts, architecture diagrams, sequence diagrams, or any visual diagrams. Handles XML structure, styling, fonts (Noto Sans JP), arrows, connectors, and PNG export.

skill-installer

from akiojin/llmlb

Install Codex skills into $CODEX_HOME/skills from a curated list or a GitHub repo path. Use when a user asks to list installable skills, install a curated skill, or install a skill from another repo (including private repos).

skill-creator

from akiojin/llmlb

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Codex's capabilities with specialized knowledge, workflows, or tool integrations.

plan

from akiojin/llmlb

Generate a plan for how an agent should accomplish a complex coding task. Use when a user asks for a plan, and optionally when they want to save, find, read, update, or delete plan files in $CODEX_HOME/plans (default ~/.codex/plans).

web-design-guidelines

from akiojin/llmlb

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".

vercel-react-best-practices

from akiojin/llmlb

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.