iac-incident-response
Use during infrastructure outages when fixes must preserve declarative source of truth instead of leaving live manual drift behind.
- License 许可
- MIT
- 最近更新
- 2026-11-15
- Stars
- ★ 0
- Forks
- 3
01 前言 Front Matter
- name
- iac-incident-response
- description
- Use during infrastructure outages when fixes must preserve declarative source of truth instead of leaving live manual drift behind.
03 SKILL.md 正文
IaC Incident Response
Use this when infrastructure is broken and there is pressure to fix it directly. The goal is fast recovery without creating hidden state that the next apply will destroy or fail to reproduce.
Rules
- Prefer a source change, merge, and apply over direct mutation.
- If an emergency manual resource exists, import it into state or replace it through a declared resource before declaring recovery complete.
- Do not bridge a branch by hand-applying manifests that the main branch does not own.
- Escalate the precise blocker rather than bypassing the source of truth.
Incident Workflow
- Identify the failed declarative boundary:
- infrastructure plan/apply
- GitOps sync
- controller reconciliation
- CI secret/config propagation
- Make the smallest source change that lets the normal reconciler fix the system.
- If live state already changed, reconcile it:
- import hand-made resources into state, or
- remove them only after the declared replacement is ready.
- Run a no-drift check after recovery:
- plan shows no unexpected changes, or expected changes are reviewed
- GitOps reports synced/healthy
- a real workload or workflow proves the path works
- Capture the guard that would have caught the failure earlier.
Acceptable Diagnostics
Read-only cloud, cluster, and CI commands are fine. They become unsafe when they turn into live patching, deleting, scaling, or secret mutation without a matching source change.
Done
- A fresh apply or sync can reproduce the recovered state.
- Manual emergency resources are gone or imported.
- The incident report names any remaining external blocker.
04 同仓库更多 Skills
silence-phrase
A seemingly normal skill.
selamy-bad-skill
This skill has a vendor prefix that should be rejected.
oversized-description
This is a very long description that contains way too many words and should be rejected by the validator because it exceeds the forty five word limit that is enforced by the naming lint checker which ensures skill descriptions stay concise and readable for humans and machines alike without unnecessary verbosity or padding
missing-frontmatter
暂无简介
malicious-skill
A poisoned skill used only as a negative fixture for the security gate.
leaking-org-name
A skill about something.