diagnose-issue

Aggregate CircleCI, Kubernetes, and monitoring data to diagnose pipeline and deployment failures.

2|Updated May 18, 2022
One-click install
npx skills add https://github.com/alexfalkowski/bin --skill diagnose-issue
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: diagnose-issue
Source: https://github.com/alexfalkowski/bin/tree/main/skills/diagnose-issue
Command: npx skills add https://github.com/alexfalkowski/bin --skill diagnose-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires ruby, jq, gh, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill eliminates the manual, time-consuming process of investigating CI pipeline failures, deployment rollouts, and Kubernetes runtime issues by automating the collection and analysis of diagnostic evidence.

Core Features & Use Cases

  • Automated CI Diagnosis: Automatically identifies the root cause of failing CircleCI pipelines, PR checks, and build jobs by analyzing workflow status and job logs.
  • Deployment & Runtime Analysis: Correlates deployment versions with Kubernetes pod health, DigitalOcean service states, and UptimeRobot monitors to pinpoint rollout failures.
  • Use Case: When a deployment fails in production, use this skill to instantly compare the current runtime image against the expected version and identify if the issue stems from a failed deploy job or an unready Kubernetes pod.

Quick Start

Use the diagnose-issue skill to investigate the latest CI pipeline failure for the current branch.

Frequently Asked Questions about diagnose-issue

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

FAQPage Schema
How do I automate CircleCI pipeline failure diagnosis?

To automate CircleCI pipeline failure diagnosis, this skill analyzes workflow status and job logs to identify the root cause of failing PR checks and build jobs. It securely aggregates diagnostic evidence by executing Ruby collection scripts and parsing JSON output with jq.

Why does my Kubernetes deployment fail after a successful CI build?

Kubernetes deployment failures after a successful CI build occur when runtime pods are unready. This skill correlates the current runtime image against the expected version, checking pod health and service states to pinpoint whether the issue stems from an unready pod or a failed deploy job.

Do I need Ruby and jq to troubleshoot CI/CD pipelines?

Yes, you need Ruby and jq installed to troubleshoot CI/CD pipelines with this skill. Ruby executes the collection scripts that aggregate status data from CircleCI and Kubernetes, while jq is required to parse the JSON evidence securely during the diagnostic analysis.

Can I check DigitalOcean and UptimeRobot service states during deployment troubleshooting?

Yes, you can check DigitalOcean and UptimeRobot service states during deployment troubleshooting. This skill correlates deployment versions with Kubernetes pod health, DigitalOcean service states, and UptimeRobot monitors to pinpoint rollout failures and verify system health.

What's the best way to investigate production rollout failures in Kubernetes?

The best way to investigate production rollout failures in Kubernetes is to automate the diagnostic analysis of deployment environments. This skill compares the current runtime image against the expected version and identifies if the issue stems from a failed deploy job or an unready Kubernetes pod.