devops-troubleshooter

Diagnose DevOps incidents and infrastructure failures using logs, metrics, and traces.

Updated May 5, 2026
One-click install
npx skills add https://github.com/Movchanets/Microservices_Learning --skill devops-troubleshooter-movchanets
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: devops-troubleshooter
Source: https://github.com/Movchanets/Microservices_Learning/tree/main/.agents/skills/devops-troubleshooter
Command: npx skills add https://github.com/Movchanets/Microservices_Learning --skill devops-troubleshooter-movchanets

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps investigate, diagnose, and resolve DevOps and infrastructure incidents quickly, reducing downtime and guesswork during outages, failures, and performance regressions.

Core Features & Use Cases

  • Incident Triage: Rapidly narrow down the most likely cause of service degradation using logs, metrics, traces, and system state.
  • Infrastructure Debugging: Troubleshoot containers, Kubernetes workloads, networking, DNS, storage, and cloud platform issues.
  • CI/CD and Deployment Recovery: Analyze build failures, deployment errors, configuration drift, and rollback needs in delivery pipelines.
  • Use Case: A production API is returning intermittent 504s; use this Skill to inspect observability signals, isolate the failing dependency, and recommend a minimal-risk fix.

Quick Start

Use the devops-troubleshooter skill to diagnose the outage, identify the root cause, and recommend verified remediation steps.

Frequently Asked Questions about devops-troubleshooter

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

FAQPage Schema
How do I troubleshoot Kubernetes workload failures and intermittent 504 errors?

Diagnosing Kubernetes workload failures and intermittent 504 errors requires analyzing observability signals like logs, metrics, and traces to isolate failing dependencies and recommend a verified remediation fix.

What is the best way to analyze CI/CD pipeline deployment failures and configuration drift?

Analyzing CI/CD pipeline deployment failures and configuration drift requires examining build errors and system state to identify root causes and determine necessary rollback recovery steps.

How do I perform root-cause-analysis for cloud-native infrastructure outages and performance regressions?

Performing root-cause-analysis for cloud-native infrastructure outages involves correlating distributed traces and metrics to narrow down likely causes of service degradation and provide actionable remediation guidance.

Can I use this approach to debug container networking and DNS issues in distributed services?

Yes, you can debug container networking and DNS issues in distributed services by investigating infrastructure failures, correlating observability data, and validating system state to resolve outages.

Does incident response troubleshooting work without dedicated observability stacks?

Incident response troubleshooting heavily relies on observability stacks for log analysis, metrics correlation, and tracing, making it difficult to isolate root causes without dedicated telemetry data.