Incident Postmortem
Independent PiSkill directory guide. The original skill remains hosted by GitHub Awesome Copilot.
What is Incident Postmortem?
Produces an evidence-based incident postmortem with timeline, impact, contributing factors, root cause, corrective actions, owners, and follow-up verification.
Compatible tools
Related skills
Bug Reproduction Brief
Turns a vague or intermittent bug report into a minimal, evidence-backed reproduction with environment details, steps, expected versus actual behavior, and a focused basis for debugging.
Azure Diagnostics
Investigates Azure application and infrastructure failures using resource state, logs, metrics, configuration, and dependency evidence, then recommends scoped remediation.
Microsoft DebugView
Uses focused diagnostics and debugging evidence to investigate application behavior, logs, failures, and runtime state without replacing root-cause analysis with speculative fixes.
Sentry Issue Fixing
Investigates Sentry issues from stack traces, events, breadcrumbs, releases, and repository context, then validates a focused fix instead of guessing from the headline.
Systematic Debugging
Guides agents through root-cause-first debugging for test failures, production bugs, performance problems, build failures, and unexpected behavior instead of guessing at fixes.
Agentic Eval
Provides patterns for evaluating and improving AI-agent outputs using self-critique, evaluator-optimizer loops, test-driven refinement, rubrics, and LLM-as-judge techniques.