OpenClaw

incident-hotfix

Coder-focused incident response and hotfix execution for production issues. Use when you need reproducible triage, patch/rollback decisions, CI-safe hotfix branches, evidence capture, and postmortem action tracking tied to code changes.

broedkrummen0 来源安装数☆ 0 仓库 Stars

查看来源 ↗安装与使用 SKILL.md ↗

安装与使用

请根据来源仓库和你的 AI 工具说明安装此技能。先阅读技能文件和依赖要求，再添加到工作流。

SkillHub CLI

skillhub install broedkrummen/incident-hotfix

打开来源仓库，查看说明和兼容环境后，按来源提供的命令或步骤安装。

将来源链接提供给你的 Agent，让它先读取说明、核对依赖，并向你说明将执行的安装步骤。

查看来源 ↗使用指南

技能说明

Incident Hotfix

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

Workflow

Classify severity using references/severity-matrix.md
Create hotfix branch from current production tag/commit
Reproduce and isolate with minimal failing test
Patch with rollback plan
Run focused CI checks
Capture evidence bundle
Merge + verify + postmortem actions

Step 1 — Create incident workspace

bash scripts/start_hotfix.sh --id INC-1234 --base main

This creates:

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

Step 2 — Evidence capture

bash scripts/capture_evidence.sh --id INC-1234

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 ROLLBACK.md
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

docs/incidents/<id>/TIMELINE.md
docs/incidents/<id>/ROLLBACK.md
docs/incidents/<id>/ACTIONS.md
docs/incidents/<id>/evidence/ 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.

来源信息

Source: github
Repository: openclaw/skills
Path: skills/broedkrummen/incident-hotfix
Version: —
Commit: 9a25544d8e0c8ae5212bc32ee862a631e4084035
分类来源: rules
状态: active
可见性: public

这些信息来自收录时的来源分析，可能滞后；使用前请核对最新来源文件。

来源内容

SKILL.md

# Incident Hotfix

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

## Workflow

1. **Classify severity** using `references/severity-matrix.md`
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

```bash
bash scripts/start_hotfix.sh --id INC-1234 --base main
```

This creates:
- `hotfix/INC-1234-<slug>` branch
- `docs/incidents/INC-1234/` folder
- starter files for timeline, rollback, and actions

## Step 2 — Evidence capture

```bash
bash scripts/capture_evidence.sh --id INC-1234
```

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 `ROLLBACK.md`
- 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

- `docs/incidents/<id>/TIMELINE.md`
- `docs/incidents/<id>/ROLLBACK.md`
- `docs/incidents/<id>/ACTIONS.md`
- `docs/incidents/<id>/evidence/` 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.

搜索