Incident Hotfix

Use this alongside broader incident-response skills when code-level action is required.

Workflow

1. 1. Classify severity using INLINECODE0
2. Create hotfix branch from current production tag/commit
3. Reproduce and isolate with minimal failing test
4. Patch with rollback plan
5. Run focused CI checks
6. Capture evidence bundle
7. Merge + verify + postmortem actions

Step 1 — Create incident workspace

CODEBLOCK0

This creates:

• - hotfix/INC-1234-<slug> branch
• INLINECODE2 folder
• starter files for timeline, rollback, and actions

Step 2 — Evidence capture

CODEBLOCK1

Collects into docs/incidents/INC-1234/evidence/:

• - latest commits + diff summary
• changed files list
• local env snapshot (safe subset)
• test output logs

Step 3 — Patch gate

Before PR/merge, ensure:

• - failing case reproduced (or clearly documented)
• minimal patch scope
• rollback command documented in INLINECODE4
• focused tests pass + no new lint/type failures

Step 4 — Postmortem actions

Use references/action-template.md to convert findings into concrete tasks:

• - owner
• due date
• verification criteria

Required outputs

• - INLINECODE6
• INLINECODE7
• INLINECODE8
• INLINECODE9 bundle

Notes

• - Prefer smallest safe patch over broad refactor during incident.
• If root cause is uncertain, ship containment first, then permanent fix.
• Never merge hotfix without rollback path.