agentleFS
Sign inStart free
caiaffacaiaffa/claude-code-ultimate-engineering-system/skills/incident-response/SKILL.md

incident-response

Skill17 starsChanged 58 days agoMITView on GitHub

Run a production incident end to end — triage, contain, investigate, resolve — then close the loop with a blameless postmortem, failure-mode prevention, and updated standards.

81 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use background-jobs, data-modeling and 9 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • YepAPISkill

    background-jobs

    Queue workers with BullMQ/Inngest/Trigger.dev, job retries, dead letter queues, concurrency.

    Also in 4 projects that use this

  • MicrosoftSkill

    data-modeling

    Use when the app needs to store or read data — records, a database, entities, CRUD, lists, "save/remember X", or per-user data with row-level security. This app's data layer is Rayfin's: you declare entities as TypeScript classes with decorators in rayfin/data/, register them in the schema, and read/write them through the typed rayfin-client. Covers: defining an @entity, field decorators, registering it, per-entity access with @role, owner-only row-level security, and the client query/mutation API. Triggers: data, database, model, entity, schema, table, record, CRUD, create, read, update, delete, list, store, save, persist, per-user, row-level security, RLS, access control, ownership.

    Also in 7 projects that use this

  • YepAPISkill

    data-pipelines

    ETL patterns, cron scheduling, queue-based processing, and batch jobs with Inngest/BullMQ.

    Also in 4 projects that use this

  • mmondoraSkill

    infrastructure-as-code

    Infrastructure as Code with Terraform and Pulumi. State management, modularity, drift detection, secrets handling. Use when provisioning cloud resources, writing Terraform/Pulumi modules, or managing infrastructure configuration.

    Also in 5 projects that use this

  • csiddhant796-blipSkill

    threat-detection

    Use when hunting for threats in an environment, analyzing IOCs, or detecting behavioral anomalies in telemetry. Covers hypothesis-driven threat hunting, IOC sweep generation, z-score anomaly detection, and MITRE ATT&CK-mapped signal prioritization.

    Also in 3 projects that use this

  • motao123Skill

    browser-verification

    Use when a change needs browser-level evidence such as UI flow checks, form interaction validation, console inspection, or end-to-end smoke verification. This skill focuses on observable behavior instead of code assumptions.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 4 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 68 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Stop user impact fast, then make the same failure impossible to repeat.

    line 8
  2. Distinctive:

    Document the timeline as you go.

    line 30
  3. Very specific:

    Write it using ~/.claude/engineering/POSTMORTEM_TEMPLATE.md (Kovi's standard template).

    line 33
  4. Very specific:

    Never invent numbers, VINs, timestamps, or names — mark TBD instead.

    line 36
  5. Distinctive:

    Remove the template's instruction block in the finished postmortem.

    line 38
  6. Distinctive:

    Update the relevant governance doc so the standard now covers it.

    line 45

“Common” is measured: kept by at least 6 in 10 of the 68 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Mission

Stop user impact fast, then make the same failure impossible to repeat.

When to use

  • A production incident: outage, latency spike, error spike, data issue.
  • Post-incident learning and prevention.

Handoff

  • Receives from: orchestrator (incident category).
  • Hands off to: systematic-debugging (root cause), release-planning (fix rollout).

Phase 1 — Triage & contain (URGENT)

  1. Triage: user impact? blast radius? getting worse?
  2. Contain BEFORE diagnosing: rollback, feature-flag off, rate-limit. Mitigation beats diagnosis when users are impacted.
  3. Declare severity. Assign an incident lead and a comms owner.

Phase 2 — Investigate

  • Hand the root cause to systematic-debugging: top 3 hypotheses, one signal each.
  • Gather traces, metrics, logs around the start time.
  • Confirm the cause before claiming resolution.

Phase 3 — Resolve

  • Confirm user impact has ended (with a signal, not a feeling).
  • Document the timeline as you go.

Phase 4 — Blameless postmortem

  • Write it using ~/.claude/engineering/POSTMORTEM_TEMPLATE.md (Kovi's standard template).
  • Blameless: describe systems and decisions, never blame a person.
  • PT-BR body; identifiers, queries, and service names in English.
  • Never invent numbers, VINs, timestamps, or names — mark TBD instead.
  • Fill the 5 Whys until the systemic cause; action items each get an owner and date.
  • Remove the template's instruction block in the finished postmortem.

Phase 5 — Failure-mode prevention

For the failure that occurred, ask:

  • What detection would have caught this sooner? (alert + threshold)
  • What guardrail would have prevented it? (test, invariant, gate)
  • What other code has the same failure mode? Update the relevant governance doc so the standard now covers it.

Red flags

  • Diagnosing while users are still impacted.
  • "Monitor closely" with no named signal/threshold.
  • Postmortem with no class-level prevention.

Output

Incident timeline, confirmed root cause, mitigation applied, postmortem with owned action items, standards updated.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free