agentleFS
Sign inStart free
prestariusprestarius/jet-skills-stack/skills/postmortem/SKILL.md

postmortem

Skill1 starsChanged 2 months agoMITView on GitHub

Write a blameless incident postmortem — impact, timeline, contributing factors, what went well/poorly, concrete follow-up actions. Use whenever the user says "postmortem", "incident review", "RCA", "write up this outage", or when a diagnosing-bugs session ends on an incident that deserves a durable record.

44 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use hypothesis-driven-debugging, organize and 8 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.
  • Sturla22Skill

    hypothesis-driven-debugging

    Debug by ranking concrete hypotheses and running discriminating checks. Use when a bug is hard to localize, many plausible failure points exist, logs are noisy or misleading, a symptom appears intermittently, or trial-and-error edits haven't worked.

    Also in 3 projects that use this

  • seongjaeryuSkill

    organize

    Organize knowledge into Sets

    Also in 3 projects that use this

  • SaluteYBSkill

    skill-eval

    Evaluate, tune, and regression-check AgentSkills. Use when creating a new skill or improving an existing one and you need structured should-trigger, should-not-trigger, boundary-case, and execution-quality examples. Also use when auditing overlapping skills and sharpening trigger descriptions before release.

    Also in 3 projects that use this

  • neurofooSkill

    premortem

    Pre-mortem analysis that imagines a plan has failed, then works backward to identify causes and preventions. Use before launches, major decisions, or risky initiatives to surface hidden risks.

    Also in 3 projects that use this

  • AnthropicSkill

    incident-response

    Run an incident response workflow — triage, communicate, and write postmortem. Trigger with "we have an incident", "production is down", an alert that needs severity assessment, a status update mid-incident, or when writing a blameless postmortem after resolution.

    Also in 4 projects that use this

  • iovisorSkill

    evolve

    Evolve uBPF through a gated spec-first workflow that propagates approved changes through requirements, design, validation, implementation, and RFC alignment artifacts.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 40 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read ./CONTEXT.md if present.

    line 5
  2. Distinctive:

    If the fix isn't verified yet, say so in the summary.

    line 22

“Common” is measured: kept by at least 6 in 10 of the 40 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

Read ./CONTEXT.md if present. Gather facts from the conversation (especially any diagnosing-bugs output), logs, and whatever the user provides. One incident per document.

Structure:

  1. Summary — severity, duration, user impact, one-line cause. Up front, no suspense.
  2. Timeline — absolute timestamps (date + time + zone), from first signal to resolution. Include detection lag and mitigation time explicitly.
  3. Contributing factors — plural by default; resist the single "root cause". Cover the trigger, why defenses didn't catch it, and what made recovery slow.
  4. What went well / what went poorly — honest, short.
  5. Follow-up actions — concrete and verifiable, each preventing a contributing factor or shortening detection/recovery. Written so the to-tickets skill can turn them into tickets.

Rules:

  • Blameless: name systems, gaps, and missing guardrails — never people. "The deploy pipeline allowed X", not "Y pushed without checking".
  • Facts only; mark every unknown TODO: instead of reconstructing a plausible story.
  • If the fix isn't verified yet, say so in the summary.

Offer (opt-in): file via the obsidian-note skill; capture a durable decision via the domain-modeling skill; turn follow-ups into tickets via the to-tickets skill.

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.

Reviews can't be read right now.

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