coding-operational-issue-diagnostics

Diagnose runtime and deployment failures using read-only evidence from Docker, Kubernetes, and Azure.

10|1|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/marcocello/dot-codex --skill coding-operational-issue-diagnostics
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coding-operational-issue-diagnostics
Source: https://github.com/marcocello/dot-codex/tree/main/skills/coding-operational-issue-diagnostics
Command: npx skills add https://github.com/marcocello/dot-codex --skill coding-operational-issue-diagnostics

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps diagnose runtime, deployment, and infrastructure issues by collecting safe, read-only evidence before any code or environment changes are made.

Core Features & Use Cases

  • Local runtime checks: Inspect Python, processes, ports, Docker, and PostgreSQL readiness when a problem can be reproduced on a developer machine.
  • Cloud and cluster diagnostics: Gather bounded evidence from Azure, Kubernetes, and Static Web Apps without performing destructive operations.
  • Failure narrowing: Correlate logs, events, and timestamps to identify the most likely cause of crashes, failed deployments, or connectivity problems.
  • Use case: A service returns 502 in production, and this Skill helps compare pod health, ingress state, recent events, and logs before any remediation is attempted.

Quick Start

Use the coding-operational-issue-diagnostics skill to investigate this failure with read-only local, Docker, PostgreSQL, Kubernetes, and Azure checks.

Frequently Asked Questions about coding-operational-issue-diagnostics

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

FAQPage Schema
How do I diagnose a Kubernetes crash loop without modifying the cluster?

Diagnose Kubernetes crash loops by collecting read-only evidence from pod health, events, and logs. This approach safely correlates deployment failures and ingress errors without performing destructive operations or changing the environment.

What is the best way to investigate a production 502 error across Azure and Docker?

Investigate production 502 errors by gathering bounded read-only evidence across Azure, Docker, and Kubernetes. Correlate logs, events, and timestamps to identify the likely cause of connectivity problems before attempting any remediation.

Can I check PostgreSQL readiness safely during a local runtime reproduction?

Check PostgreSQL readiness safely during local runtime reproductions by collecting read-only evidence. Inspect local processes, ports, and database state to narrow down failures before making any code or environment changes.

Does this diagnostics approach work for Azure Static Web App deployment failures?

Diagnostics for Azure Static Web App deployment failures work by collecting read-only cloud environment evidence. Gather bounded subscription context and correlate events to identify mismatches without executing destructive operations.

How do I correlate logs and events to narrow down cloud environment mismatches?

Correlate logs and events to narrow down cloud environment mismatches by applying bounded command execution and redacted output handling. Collect read-only evidence across Azure and Kubernetes to identify the most likely failure cause.