iac-incident-response
Skill0 starsChanged 7 days agoMITView on GitHub
Use during infrastructure outages when fixes must preserve declarative source of truth instead of leaving live manual drift behind.
In this repository108 other files it gives its agents.
- adaptive-estimationSkill
- adaptive-loop-budgetingSkill
- adopt-and-deleteSkill
- adversarial-reviewSkill
- agent-drives-uiSkill
- agentic-coding-loopSkill
- agent-otel-trajectorySkill
- agents-as-iac-modulesSkill
- ascii-ui-mockupsSkill
- authoring-html-emailSkill
- authoring-skills-vs-mcpSkill
- batched-ssh-enumerationSkill
- c4-architectureSkill
- challenge-the-premiseSkill
- codegraph-bootstrapSkill
- codegraph-worktree-startupSkill
- colocated-pod-tolerationsSkill
- command-creatorSkill
- complexity-budgetsSkill
- connector-readinessSkill
- context-anchored-patchingSkill
- continuous-issue-resolutionSkill
- credential-proxySkill
- criticality-tiered-reportingSkill
- data-connector-buildingSkill
- declarative-firstSkill
- disk-pressure-forensicsSkill
- early-return-over-elseSkill
- email-triageSkill
- enums-codify-behaviorSkill
- ephemeral-workspace-lifecycleSkill
- event-sourcingSkill
- evidence-claim-boundariesSkill
- exhaustive-matchSkill
- feature-coverage-not-just-line-coverageSkill
- full-disk-forensicsSkill
- gate-before-pushSkill
- github-pr-shepherdingSkill
- graceful-shutdown-stateful-agentsSkill
- grounded-generationSkill
- iac-not-ad-hocSkill
- instrumented-service-scaffoldSkill
- interface-over-conditionalsSkill
- knowledge-routingSkill
- lean-on-oss-standardsSkill
- live-money-disciplineSkill
- live-state-verificationSkill
- loop-governance-and-learningSkill
- low-level-executor-task-specSkill
- map-dispatch-over-conditionalsSkill
- merge-conflict-disciplineSkill
- mermaid-diagramsSkill
- oke-arc-runners-opentofuSkill
- orchestrate-agySkill
- orchestrate-claudeSkill
- orchestrate-codexSkill
- orchestrate-geminiSkill
- otel-emit-at-willSkill
- parameter-designSkill
- parse-dont-validateSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 9 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use this when infrastructure is broken and there is pressure to fix it directly.
- Distinctive: line 14
Prefer a source change, merge, and apply over direct mutation.
- Distinctive: line 15
If an emergency manual resource exists, import it into state or replace it through a declared resource before declaring recovery complete.
- Distinctive: line 17
Do not bridge a branch by hand-applying manifests that the main branch does not own.
- Distinctive: line 30
If live state already changed, reconcile it:
- Distinctive: line 31
import hand-made resources into state, or
- Distinctive: line 32
remove them only after the declared replacement is ready.
- Distinctive: line 33
Run a no-drift check after recovery:
- Distinctive: line 41
Read-only cloud, cluster, and CI commands are fine.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.