Generate structured post-mortem reports from debugging sessions.
npx skills add https://github.com/alleneee/topsport-agent --skill break-loop-alleneee
Please help me install this Agent Skill. Skill: break-loop Source: https://github.com/alleneee/topsport-agent/tree/main/.agents/skills/break-loop Command: npx skills add https://github.com/alleneee/topsport-agent --skill break-loop-alleneee
Automates deep post-mortem bug analysis to break the fix-forget-repeat cycle and translate insights into actionable documentation.
After completing a debugging session, invoke this skill to generate a structured post-mortem analysis and update guide materials.
High-intent search queries and answers about installing and using this skill.
Post-mortem bug analysis is a structured review process after a debugging session to identify root causes and prevent recurrence. You need it after resolving tricky bugs to break the fix-forget-repeat cycle and capture lessons learned.
You document root cause and prevention steps by running a post-mortem analysis that categorizes the failure, proposes prevention mechanisms, and systematically expands on design and process improvements to update project documentation.
Yes, you can automate knowledge capture by invoking a post-mortem analysis skill after fixes to generate structured reports and prompt updates to thinking guides and project docs for future incident reference.
The best way to break the fix-forget-repeat cycle is to perform deep post-mortem analysis after each fix, categorizing root causes and translating insights into actionable documentation and updated prevention mechanisms.
Post-mortem analysis applies to debugging sessions after fixes of any scale, covering root-cause categorization, failure analysis, and knowledge capture to ensure both simple and complex bugs are documented for future prevention.
LonelyHerbivoreConvert completed debugging sessions into structured bug prevention guidance.
haizhouyuanConvert articles, transcripts, or reports into structured Markdown digests.
gdm257Analyze post-mortem bugs to identify root causes and prevention strategies.
s3nex-comGenerate structured post-mortem documents for P1 and P2 production incidents.
