skills.rest
mikemyl
mikemylCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

ci-debugging

Diagnoses CI/CD failures by hypothesis listing, reproduction, and environment comparison.

1|Updated Mar 22, 2026
Search Tags:#CI/CD#build issues#failure diagnosis#test pipeline#CI debugging
One-click install
npx skills add https://github.com/mikemyl/verified-development --skill ci-debugging-mikemyl
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ci-debugging
Source: https://github.com/mikemyl/verified-development/tree/main/skills/ci-debugging
Command: npx skills add https://github.com/mikemyl/verified-development --skill ci-debugging-mikemyl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a systematic approach to diagnosing CI/CD failures, build issues, or test pipeline problems.

Core Features & Use Cases

  • Hypothesis-First Diagnosis: Systematically investigates root causes of CI failures with a structured hypothesis list.
  • Local Reproduction: Encourages local reproduction of failures to ensure accuracy before pushing fixes.
  • Environment Delta Analysis: Compares CI environment differences with local settings for potential issues.
  • Error Reading: Instructs to read complete error outputs for identifying actual failure points.
  • Fix Verification: Promotes explaining and verifying fixes to ensure they address the root cause.

Quick Start

Analyze a CI failure by listing 3 potential root causes, reproducing locally, and comparing CI and local environments.

Frequently Asked Questions about ci-debugging

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

FAQPage Schema
How do I debug CI/CD pipeline failures systematically?▼

Debug CI/CD pipeline failures by listing potential root causes, reproducing the failure locally, comparing environment differences, and analyzing complete error outputs to find the actual failure point.

What causes a build to pass locally but fail in the CI environment?▼

Build failures in CI often stem from environment deltas, such as differing dependency versions or local settings. Compare your CI environment differences with local settings to identify these potential issues.

What is the best way to diagnose test pipeline issues?▼

The best way to diagnose test pipeline issues is hypothesis-first: list 3 potential root causes, reproduce the failure locally, and compare CI and local environments to verify the fix.

Why should I read the complete error output when diagnosing build issues?▼

Reading complete error outputs when diagnosing build issues is critical because it instructs you on identifying the actual failure point, ensuring your subsequent fixes address the true root cause.

Do I need to reproduce CI failures locally before pushing fixes?▼

Yes, local reproduction of CI failures is encouraged to ensure accuracy before pushing fixes. This verifies the error condition and validates that your fix addresses the root cause.

Related Skills

Explore More Software Engineering Skills→
kagentikagenti
292

rca

Automate root cause analysis by triaging CI logs, Kind, or HyperShift diagnostics.

Official
Advanced
LisztVanLisztVan
2

systematic-debugging

Diagnoses root cause of bugs and test failures before proposing fixes.

Community
Advanced
kangmominkangmomin
1

minmo-doctor-mm

Diagnose minmos-harness plugin dependencies and output a structured report.

Community
Advanced
StrategicMilkStrategicMilk

Monitoring and Alerting

Detect operational anomalies in system metrics using statistical process control.

Community
Advanced