skills.rest
nirssyan
nirssyanOFFICIAL
Explore all skills by this author →
GitHub

incident

Gather data from GlitchTip, Loki, Prometheus, and Kubernetes events to identify root causes.

Updated Aug 23, 2026
Search Tags:#debugging#metrics#kubernetes#log analysis#error investigation#incident#production issues
One-click install
npx skills add https://github.com/nirssyan/nirssyan-mono --skill incident-nirssyan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: incident
Source: https://github.com/nirssyan/nirssyan-mono/tree/main/.claude/skills/incident
Command: npx skills add https://github.com/nirssyan/nirssyan-mono --skill incident-nirssyan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the investigation of production incidents by gathering data in parallel from various sources, helping to quickly identify the root cause of issues.

Core Features & Use Cases

  • Parallel Data Gathering: Simultaneously collects information from GlitchTip (errors), Loki (logs), Prometheus (metrics), and Kubernetes events.
  • Error Analysis: Identifies specific error messages, patterns, and their frequency.
  • Infrastructure Health Check: Assesses pod status, Kubernetes events, and resource utilization (CPU).
  • Codebase Investigation: Optionally searches code for error origins and recent changes if a specific error message is provided.
  • Use Case: When a user reports that the "checkout service is down," this Skill can be invoked to gather all relevant error messages, logs, and metrics across services to pinpoint the failure.

Quick Start

Use the incident skill to investigate the current state of all services.

Frequently Asked Questions about incident

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

FAQPage Schema
How do I diagnose production incidents using Kubernetes events and Prometheus metrics?▼

To diagnose production incidents, this Skill gathers Kubernetes events and Prometheus metrics in parallel to analyze error messages, infrastructure health, and resource utilization, pinpointing root causes quickly.

Can I investigate Loki logs and GlitchTip errors simultaneously for a root cause analysis?▼

Yes, you can investigate Loki logs and GlitchTip errors simultaneously. The Skill performs parallel data gathering from both sources alongside Kubernetes events to identify error patterns and frequencies.

How do I find the root cause of a production issue if I only have an error message?▼

Finding the root cause with an error message is supported. You can provide a specific error message or GlitchTip alert ID as input, and the Skill will optionally search the codebase for error origins and recent changes.

What is the best way to check infrastructure health during a Kubernetes incident?▼

Checking infrastructure health during a Kubernetes incident is handled by assessing pod status, Kubernetes events, and CPU resource utilization metrics gathered directly from Prometheus to identify system failures.

Does this incident investigation tool support searching the codebase for recent changes?▼

Yes, incident investigation supports codebase searches. If you provide a specific error message as input, it optionally searches the code to find error origins and recent changes relevant to the production issue.

Related Skills

Explore More Software Engineering Skills→
shepard-systemshepard-system
70

obs-query

Execute PromQL and LogQL queries against Prometheus and Loki.

Official
Intermediate
unblockedunblocked
13

headless-recommend-fixes

Generate ranked remediation options for incidents from parsed context and historical fixes.

Official
Advanced
miko06miko06

document-release

Update project documentation files after shipping using Git and Bash.

Community
Advanced
terna-ccterna-cc

sentry-setup

Configure Sentry SDK and integrate Pino for automated log forwarding.

Official
Basic