Hotfix

---
name: hotfix
description: "Fast path for an urgent production fix — reproduce with a failing test, minimal fix on a hotfix branch from the release tag, mandatory security review for sensitive paths, expedited checklist, deploy and backport to main. Use for P1 production bugs."
argument-hint: "[issue description or bug id]"
user-invocable: true
allowed-tools: Read, Glob, Grep, Write, Edit, Bash, Task, AskUserQuestion
model: sonnet
---

# Hotfix

**Two kinds of urgent, one skill.** `production` (the default): something is broken for users — reproduce with a failing test, minimal fix on a hotfix branch from the release tag, expedited security gate, release. `--chore`: the toolchain is broken or in the way — a red runner, a linter that blocks every commit, a dependency that must move now. The chore path skips the release machinery and follows the chore/infra lane of `git-workflow.md`: branch `chore/<slug>`, commits `ci(…)`/`chore(…)`, a PR with `/code-review --diff` (workflow files → `devops-engineer`), and the outcome recorded as a finding or a backlog entry. Neither path is a place for a feature: work that changes what the product does is a story, however small it looks at the moment it is asked for.

Reply in the project conversation language (CLAUDE.md → Language); code, identifiers, paths and commit messages stay in English.

File writes and any mutation (git, deploy) happen only after an explicit "May I write?" / "Proceed?" — each one `AskUserQuestion` (proceed (Recommended) · show the draft/diff first · not now) → "yes"; delegated agents follow the same protocol. After the "write" answer: `touch .claude/.write-consent` (rule 7 — the consent-guard hook checks the marker).

## Phase 1: Reproduce
Branch `hotfix/<slug>` from the production tag; a failing test reproducing the bug (mandatory); impact assessment (data? security? → `security-lead` via Task).

## Phase 2: Minimal fix
Through the relevant engineer; only what is needed; test green; lint/typecheck; for sensitive paths — `appsec-engineer` review.

## Phase 3: Expedited gate
Package tests + e2e smoke; `/changelog` patch version; `/deploy` with confirmation (delegate verbs `deploy`/`rollback` by `docs/deploy-target-contract.md`); backport to the default branch (`master`/`main`, PR).

## Phase 4: Postmortem note
A short entry in `docs/ops/incidents/` (or `/incident` if there was an incident).

Verdict: `FIXED` | `BLOCKED`. Next step — one `AskUserQuestion`: `/incident` for root-cause analysis (Recommended) · backport to main · stop here.