incident-analyzing

Name: incident-analyzing
Availability: InStock
Author: Wizeline

Analyze logs and traces to identify failure origins and assess incident blast radius.

Updated Aug 27, 2026

Search Tags:#debugging #troubleshooting #root cause analysis #distributed systems #error analysis #incident management

Ready to run

npx skills add https://github.com/wizeline/sdlc-agents --skill incident-analyzing

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: incident-analyzing
Source: https://github.com/wizeline/sdlc-agents/tree/main/aicores/incident-resolution-agent/skills/incident-analyzing
Command: npx skills add https://github.com/wizeline/sdlc-agents --skill incident-analyzing

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers quickly identify the root cause of system failures by applying structured hypothesis testing and analyzing logs, traces, and system behavior.

Core Features & Use Cases

Root Cause Analysis: Systematically tests hypotheses to find the causal chain of failures.
Impact Assessment: Quantifies the blast radius of an incident, including user impact and revenue path.
Stack Trace Analysis: Identifies error patterns and their likely origins in code.
Use Case: When a critical service is down, this Skill can analyze error logs and system metrics to pinpoint whether the issue stems from a database overload, a recent deployment, or a downstream dependency failure.

Quick Start

Analyze the provided stack trace and logs to determine the root cause of the current outage.

Frequently Asked Questions about incident-analyzing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I find the root cause of an outage in distributed systems?▼

Root cause analysis in distributed systems requires structured causal hypothesis testing against logs, traces, and system behavior to identify the exact failure origin. This Skill applies that methodology to pinpoint whether failures stem from service overloads, deployments, or dependencies.

How do I analyze stack traces to identify error patterns and origins?▼

Stack trace analysis identifies error patterns and their likely origins in code by reading topology and failure pattern references. It isolates specific code segments causing exceptions to determine if issues stem from database overloads, recent deployments, or downstream dependency failures.

Can I assess the blast radius and user impact of an active incident?▼

Impact assessment quantifies the blast radius of an active incident by evaluating user impact and revenue path disruption. It maps the confirmed causal chain to determine exactly which downstream services and users are affected by the identified failure origin.

Does root cause analysis work for failures in CI pipelines and local environments?▼

Root cause analysis applies structured hypothesis testing to identify failure origins across services, CI pipelines, and local environments. It reads topology and failure pattern references to systematically trace the causal chain regardless of where the active incident originates.

What is the best way to troubleshoot a critical service down due to a downstream dependency failure?▼

Troubleshooting a critical service down requires analyzing error logs and system metrics to pinpoint whether the issue stems from a database overload, a recent deployment, or a downstream dependency failure. Structured hypothesis testing confirms the causal chain across the distributed system topology.