devops-troubleshooter

Diagnose production outages using logs, traces, and Kubernetes debugging.

23|2|Updated Jan 19, 2026
One-click install
npx skills add https://github.com/herdiansah/Antigravity-Skills-Master --skill devops-troubleshooter-herdiansah
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: devops-troubleshooter
Source: https://github.com/herdiansah/Antigravity-Skills-Master/tree/main/.agent/skills/devops-troubleshooter
Command: npx skills add https://github.com/herdiansah/Antigravity-Skills-Master --skill devops-troubleshooter-herdiansah

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill rapidly resolves production outages, system reliability issues, and complex debugging challenges by leveraging advanced observability and troubleshooting methodologies.

Core Features & Use Cases

  • Incident Response: Quickly diagnose and mitigate production incidents.
  • Root Cause Analysis: Identify the underlying causes of system failures using logs, metrics, and traces.
  • Kubernetes Debugging: Troubleshoot issues within containerized environments and Kubernetes clusters.
  • Performance Optimization: Analyze and resolve performance bottlenecks in applications and infrastructure.
  • Use Case: When a critical service experiences intermittent failures, this Skill can analyze distributed traces and logs to pinpoint the exact microservice and code path causing the issue, then suggest a fix.

Quick Start

Debug high memory usage in Kubernetes pods causing frequent OOMKills and restarts.

Frequently Asked Questions about devops-troubleshooter

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

FAQPage Schema
How do I debug high memory usage in Kubernetes pods causing frequent OOMKills?

To debug high memory usage in Kubernetes pods causing OOMKills, analyze distributed traces, metrics, and logs to pinpoint the exact microservice causing the issue, then optimize resource limits and application code.

What is the best way to perform root cause analysis for a production outage using distributed tracing?

Root cause analysis for a production outage using distributed tracing involves analyzing logs, metrics, and traces to identify the exact microservice and code path causing system failures, enabling rapid incident response and mitigation.

Can I use observability platforms to troubleshoot intermittent failures in microservices?

Yes, you can use observability platforms to troubleshoot intermittent failures in microservices by aggregating distributed traces and application logs to identify performance bottlenecks and diagnose network or system reliability issues.

How do I resolve performance bottlenecks in containerized environments during an incident response?

Resolving performance bottlenecks in containerized environments during incident response requires analyzing infrastructure metrics and Kubernetes cluster diagnostics to isolate resource contention, then applying performance optimization techniques to restore system reliability.

Why does my Kubernetes cluster experience system reliability issues despite having logs and metrics enabled?

System reliability issues in Kubernetes clusters with logs and metrics enabled often stem from incomplete distributed tracing or unanalyzed network diagnostics, preventing accurate root cause analysis for complex production outages.