Orchestrates a 14-step incident response and root cause analysis workflow.
npx skills add https://github.com/3D-Stories/rawgentic --skill rawgentic-incident
Please help me install this Agent Skill. Skill: rawgentic:incident Source: https://github.com/3D-Stories/rawgentic/tree/main/skills/incident Command: npx skills add https://github.com/3D-Stories/rawgentic --skill rawgentic-incident
This Skill provides a structured, 14-step workflow to rapidly diagnose, stabilize, and perform root cause analysis for production incidents, ensuring service restoration and preventing recurrence.
.rawgentic.json) for environment setup and diagnostics.Use the incident skill to respond to an incident where the dashboard is not loading.
High-intent search queries and answers about installing and using this skill.
A structured incident response workflow separates immediate service stabilization from in-depth root cause analysis. This process uses a 14-step approach to rapidly diagnose production issues, restore service, and conduct 5 Whys analysis to implement permanent preventive fixes.
To fix production incidents returning 500 errors, use a phased incident response workflow. Phase A focuses on rapid diagnosis and service stabilization using provided playbooks, while Phase B conducts a detailed 5 Whys analysis to establish permanent fixes and prevent future occurrences.
Yes, you can execute SRE production support workflows without external dependencies. The incident response process operates independently using project configuration files loaded from the environment, ensuring strict step-marker enforcement and guided diagnostics for rapid root cause analysis.
The best way to conduct a 5 Whys analysis is executing it as a dedicated post-incident phase. After service restoration, the workflow transitions to root cause analysis, guiding detailed 5 Whys investigations to identify underlying issues and implement preventive measures against recurrence.
Yes, a project configuration file is required for config-driven incident response operations. The workflow leverages this configuration for environment setup and diagnostics, ensuring accurate service stabilization and root cause analysis during production debugging and incident management.
Incident response workflows separate stabilization from root cause analysis to prioritize immediate service restoration. Phase A rapidly stabilizes the affected service using playbooks, while Phase B focuses entirely on detailed 5 Whys analysis to ensure permanent fixes without delaying recovery.
NorkzYTExternalize Python application configuration into typed pydantic-settings validated from environment variables.
vertivolatamGuide blameless post-mortems with timeline reconstruction and 5 Whys analysis.
mtsatryanGuide metrics, logs, and trace collection with Prometheus, OpenTelemetry, and Grafana.
mozilor-technologiesAutomate root-cause debugging and fix implementation for workflow issues.