Postmortem Analysis
A postmortem (also called incident review or retrospective) is a structured process for analyzing incidents to understand what happened, why it happened, and how to prevent similar incidents in the fu
npx skills add majiayu000/claude-skill-registry --skill postmortem-analysis --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Postmortem Analysis ## Skill Profile *(Select at least one profile to enable specific modules)* - [ ] **DevOps** - [x] **Backend** - [ ] **Frontend** - [ ] **AI-RAG** - [ ] **Security Critical** ## Overview A postmortem (also called incident review or retrospective) is a structured process for analyzing incidents to understand what happened, why it happened, and how to prevent similar incidents in the future. The goal is learning, not blaming. **Core Principle**: "Blame the system, not the person. Every incident is an opportunity to learn and improve." ## Why This Matters - **<Benefit>**: <short explanation> - **<Benefit>**: <short explanation> - **<Benefit>**: <short explanation> ## Core Concepts & Rules ### 1. Core Principles - Follow established patterns and conventions - Maintain consistency across codebase - Document decisions and trade-offs ### 2. Implementation Guidelines - Start with the simplest viable solution - Iterate based on feedback and requirements - Test thoroughly before deployment ## Inputs / Outputs / Contracts * **Inputs**: - <e.g., env vars, request payload, file paths, schema> * **Entry Conditions**: - <Pre-requisites: e.g., Repo initialized, DB running, sp
- Skill Profile
- Overview
- Why This Matters
- Core Concepts & Rules
- 1. Core Principles
- 2. Implementation Guidelines
- Inputs / Outputs / Contracts
- Skill Composition
- Quick Start / Implementation Example
- Assumptions / Constraints / Non-goals
- Compatibility & Prerequisites
- Test Scenario Matrix (QA Strategy)
- Technical Guardrails & Security Threat Model
- 1. Security & Privacy (Threat Model)
What does the Postmortem Analysis skill do?
A postmortem (also called incident review or retrospective) is a structured process for analyzing incidents to understand what happened, why it happened, and how to prevent similar incidents in the fu
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill postmortem-analysis --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.