Automate post-incident analysis and generate debrief documents from codebase evidence.
npx skills add https://github.com/vladpolewoi/config76 --skill debrief-vladpolewoi
Please help me install this Agent Skill. Skill: debrief Source: https://github.com/vladpolewoi/config76/tree/main/claude/skills/debrief Command: npx skills add https://github.com/vladpolewoi/config76 --skill debrief-vladpolewoi
This Skill streamlines the creation of a structured post-incident analysis, helping you quickly document timelines, root causes, and actionable follow-ups.
Use the debrief skill to analyze the incident described in the 'error-logs.txt' file and generate a debrief document.
High-intent search queries and answers about installing and using this skill.
Automate post-incident analysis by using a skill that gathers incident context, collects codebase evidence, performs root cause analysis, and generates actionable follow-ups. It streamlines creating structured debrief documents directly within Claude Code.
A structured post-incident debrief document includes a detailed incident timeline, the identified root cause, contributing factors, and specific actionable follow-up items for prevention, detection, and response.
Generate root cause analysis by feeding error logs and context to an automated process that queries Git operations and analyzes the codebase to synthesize evidence, identify the root cause, and document contributing factors.
Post-incident analysis automates evidence collection directly from the codebase, but requires providing initial incident context like error logs to accurately synthesize evidence and identify the root cause.
The best way to create actionable incident response follow-ups is to synthesize collected codebase evidence to generate specific, assignable action items focused on incident prevention, detection, and response strategies.
krzemienskiAnalyze historical validation runs and deployments to compute false pass/fail rates and confidence scores.
saintgo7Create standardized 7-section incident postmortems with 5-Why root cause analysis.
i3ringitAnalyze git history to trace file evolution, contributors, and change patterns.
thoreinsteinGenerates blameless postmortems with root-cause analysis for software incidents.
