agentsclimarketplace

Post mortem

Skill searayca/claude-skills/skills/post_mortem

Reusable slash-command skills for Claude Code — document generation, changelogs, post-mortems, copyright headers, and more

Install
npx -y skills add searayca/claude-skills --skill post_mortem

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Generate a detailed post-mortem analysis after a debugging session or incident, capturing what failed, what worked, and lessons learned

SKILL.md

2.0 KB, as published. Nobody here has run it

Post-Mortem Generator

Generate a detailed post-mortem analysis after a debugging session or incident.

When to Use

Use this command after:

  • A debugging session that took longer than expected
  • An incident or outage
  • A complex problem that was finally resolved
  • Any situation where we want to capture lessons learned

Instructions

  1. Review the conversation history to identify:

    • The original problem/request
    • What was tried and failed
    • What finally worked
    • Time spent vs expected

  2. Generate a post-mortem document with these sections:

    Header

    • Date
    • Issue summary (one line)
    • Resolution time (actual vs expected)

    The Problem

    • Clear description of what the user wanted
    • Why it seemed simple

    What Went Wrong

    • Number each failure point
    • Include code snippets showing the problematic code/config
    • Explain WHY each approach failed

    The Solution

    • The actual fix (with code)
    • Why this worked when other approaches didn't

    What We Learned

    • Numbered list of technical lessons
    • Be specific and actionable

    What To Do Differently

    • Organized by phase: Before/During/After
    • Include specific commands or checks to run

    Time Cost

    • Honest assessment of wasted time
    • Root causes of the delay

    Key Takeaway

    • One memorable sentence summarizing the main lesson

  3. Save the document to docs/postmortem_[brief_description].md

  4. Ask the user if any lessons should be added to CLAUDE.md for future reference

Output Format

Use markdown with clear headers, code blocks, and bullet points. Keep it scannable but detailed enough to be useful months later.

Example Filename

  • postmortem_dashboard_width.md
  • postmortem_api_timeout.md
  • postmortem_deploy_failure.md

Gives 1 of the 12 instructions most incident response skills give

Counted across 224 of the 224 authors here whose files we hold, read 2026-08-06

  • Conduct a blameless postmortem within 48 hoursin 24 of 224, across 14 files
  • perform root cause analysis using five whysin 24 of 224, across 20 files
  • write a blameless postmortemin 22 of 224, across 19 files
  • Update stakeholders every 15 to 30 minutesin 19 of 224, across 9 files
  • assign an owner and due date to every action itemin 18 of 224
  • Classify incident severity within 5 minutesin 17 of 224, across 7 files
  • Create a post-mortem documenthere, and in 17 of 224, across 14 files
  • Assign all action items with deadlinesin 14 of 224, across 6 files
  • Implement immediate mitigation prioritizing user restorationin 13 of 224, across 3 files
  • assign one incident commanderin 12 of 224
  • Stop and ask for clarification if inputs are missingin 10 of 224, across 2 files
  • Escalate earlyin 10 of 224, across 2 files

Said here and by no other author read

  • review conversation history
  • identify original problem
  • identify failed attempts
  • identify successful solution
  • assess time spent
  • number each failure point

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.