infra-debug

Diagnoses Kubernetes deployment and infrastructure issues via pod health checks, logs, and events.

16|11|Updated Jun 12, 2025
One-click install
npx skills add https://github.com/liwoo/goravel-inertia-tw-starter --skill infra-debug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: infra-debug
Source: https://github.com/liwoo/goravel-inertia-tw-starter/tree/main/.claude/skills/infra-debug
Command: npx skills add https://github.com/liwoo/goravel-inertia-tw-starter --skill infra-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps operators debug infrastructure and deployment issues by inspecting pods, logs, events, and networking to diagnose why applications are unhealthy or misconfigured.

Core Features & Use Cases

  • Pod status checks across clusters to identify non-running containers and restarts.
  • Log and event analysis to trace root causes of failures.
  • Ingress and networking troubleshooting to verify routing and TLS configurations.
  • Guided diagnostics for common Kubernetes and Docker deployments in staging or production environments.

Quick Start

Run infra-debug staging pods to inspect pod status and logs for failing deployments.

Frequently Asked Questions about infra-debug

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

FAQPage Schema
How do I diagnose unhealthy Kubernetes pods in a production deployment?

To diagnose unhealthy Kubernetes pods, you inspect pod statuses, review container logs, and check cluster events to identify non-running containers or restart loops. This pinpoints why applications are misconfigured or failing in production environments.

What's the best way to troubleshoot Kubernetes ingress and networking routing issues?

Troubleshooting Kubernetes ingress and networking issues involves inspecting routing configurations and TLS settings to verify traffic flow. Analyzing cluster events helps trace misconfigurations affecting application connectivity across namespaces.

Do I need kubectl access to check pod status and restarts across namespaces?

Yes, you need kubectl access and context switching permissions across namespaces to check pod status and restarts. This access enables guided diagnostics to parse pod statuses and view logs for failing deployments.

Why are my staging deployment containers failing to start and how can I trace the root cause?

Your staging deployment containers may be failing due to misconfigurations or application errors. You can trace the root cause by running a guided diagnostic that inspects pod health, reviews application logs, and interprets cluster events.