skills.rest
cyberpunk042
cyberpunk042COMMUNITY
Explore all skills by this author →
GitHub

ops-incident

Collect logs, metrics, and changes to diagnose incident root causes.

Updated Mar 26, 2026
Search Tags:#debugging#logs#post-mortem#diagnose#root-cause#incident#incident-response
One-click install
npx skills add https://github.com/cyberpunk042/devops-expert-local-ai --skill ops-incident
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ops-incident
Source: https://github.com/cyberpunk042/devops-expert-local-ai/tree/main/.claude/skills/ops-incident
Command: npx skills add https://github.com/cyberpunk042/devops-expert-local-ai --skill ops-incident

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Incident response workflows to quickly diagnose outages, fix defects, and document a formal incident report.

Core Features & Use Cases

  • Gather diagnostics: logs, error messages, metrics, and recent changes
  • Root cause analysis and fix proposals: trace symptoms to their causes and suggest code/config changes
  • Generate incident reports: timelines, root cause, remediation steps, and prevention plans
  • Use Case: On outage, collect evidence, identify failing component, implement fix, and communicate findings

Quick Start

Run the incident response workflow against the latest incident to diagnose, fix, and report.

Frequently Asked Questions about ops-incident

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

FAQPage Schema
How do I diagnose a root cause for a software incident using logs and metrics?▼

Yes, you can apply incident response workflows to both development and production environments for on-call outages and service degradations. The process adapts to collect relevant diagnostics and propose fixes regardless of the deployment stage or infrastructure scale.

How do I generate a post-mortem report after resolving an outage?▼

You generate a post-mortem report by compiling the incident timeline, root cause, remediation steps, and prevention plans into a formal document. This records the diagnostic evidence and fixes applied, ensuring clear communication of findings and future mitigation strategies.

What is the best way to structure incident response workflows for on-call outages?▼

The best way to structure incident response workflows is through a phased approach: data gathering, root-cause analysis, remediation proposals, and formal reporting. This sequence ensures you collect evidence, identify failing components, implement fixes, and document the resolution systematically.

Can I use this incident response workflow for service degradations in development environments?▼

Yes, you can apply incident response workflows to both development and production environments for on-call outages and service degradations. The process adapts to collect relevant diagnostics and propose fixes regardless of the deployment stage or infrastructure scale.

Related Skills

Explore More Software Engineering Skills→
clawpod-appclawpod-app
46

infrastructure-audit

Audit infrastructure health using DORA metrics from deployment and incident data.

Community
Intermediate
GTC6244GTC6244

cso

Audit project security posture across infrastructure, CI/CD, and dependencies.

Community
Advanced
bobmatnycbobmatnyc
68

datadog-observability

Integrate Datadog APM, logs, metrics, synthetics, and RUM for full-stack observability.

Community
Advanced
JansenAnalyticsJansenAnalytics
5

error-monitor

Monitor application logs and stderr to detect errors, crashes, and exceptions.

Community
Intermediate