After fixing a bug, you need to write a clear record. This skill helps you create a post-mortem for other engineers and for your future self. It captures the root cause, how the bug was fixed, and how it slipped through testing.
Engineers benefit the most. The post-mortem saves time when someone encounters a similar issue later. It also helps the team learn from mistakes without repeating them.
Use this skill after a debug session lands a real fix. Write it before you close the bug ticket. The record includes code identifiers and validation steps so anyone can understand the fix quickly.
Global
mkdir -p ~/.claude/skills/post-mortemProject
mkdir -p .claude/skills/post-mortemSource Repository
Azure Diagnosticsmicrosoft/azure-skills
Debug Azure production issues with systematic diagnostics and AI-powered tools
Azure Messagingmicrosoft/azure-skills
Troubleshoot and fix Azure messaging SDK errors for Event Hubs and Service Bus
Use My Browserxixu-me/skills
Work inside your live browser session for real page inspection and debugging
Diagnosemattpocock/skills
A step-by-step debug loop for finding and fixing hard bugs
Diagnosing Bugsmattpocock/skills
Build a tight feedback loop to find any bug fast
Systematic Debuggingobra/superpowers
Find the root cause of every bug before attempting any fix to save time
Safe Debuglllllllama/rigorpilot-skills
Debug deep learning failures safely with conservative diagnosis and minimal patches
Firebase Crashlyticsfirebase/agent-skills
Set up crash reporting for your Android or iOS app with ease