cicd-diagnostics

Diagnose GitHub Actions CI/CD failures and generate issue reports.

949|481|Updated Mar 15, 2012
One-click install
npx skills add https://github.com/dotCMS/core --skill cicd-diagnostics
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cicd-diagnostics
Source: https://github.com/dotCMS/core/tree/main/.claude/skills/cicd-diagnostics
Command: npx skills add https://github.com/dotCMS/core --skill cicd-diagnostics

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

CI/CD failures are complex, time-consuming to diagnose, and block development. This skill automates the entire diagnostic process, from identifying failed jobs to pinpointing root causes and suggesting fixes, allowing engineers to resolve issues rapidly and keep the pipeline flowing.

Core Features & Use Cases

  • Intelligent Failure Analysis: Automatically identifies failed jobs, extracts critical errors from massive logs, and classifies failures (new, flaky, infrastructure).
  • Root Cause Determination: Pinpoints the exact cause of failure, whether it's a code defect, a flaky test, a timing issue, or an infrastructure problem.
  • GitHub Integration: Searches existing issues, creates detailed new issues with proper labels, and links to relevant PRs and commits.
  • Use Case: A developer's PR build fails. Instead of manually sifting through gigabytes of logs, they use this skill to get an immediate, comprehensive report detailing the exact test that failed, why it failed (e.g., a race condition), and a link to a known issue or a recommended fix.

Quick Start

Analyze the latest failed CI/CD run for my current pull request.

Frequently Asked Questions about cicd-diagnostics

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

FAQPage Schema
How do I debug CI/CD failures in GitHub Actions workflows?

CI/CD debugging extracts root causes from failed GitHub Actions jobs by analyzing logs, identifying syntax errors, and classifying failures as code defects, flaky tests, or infrastructure issues. This skill automates log extraction, cross-run comparisons, and generates evidence-backed diagnostic reports with actionable recommendations.

Can I automate root cause analysis for build failures across multiple runs?

Yes. Automated root cause analysis compares logs across multiple CI/CD runs to detect patterns, classify failures (new vs. recurring flaky tests), and pinpoint exact causes. The skill integrates with GitHub CLI and jq to extract structured data from workflow logs and generate linked issue reports.

How do I identify why tests are flaky in GitHub Actions?

Flaky test diagnosis isolates timing issues, race conditions, and intermittent failures by analyzing logs from repeated runs and extracting error patterns. This skill applies tiered log extraction to pinpoint failure behavior, distinguishing flaky tests from permanent code defects.

What's the best way to create detailed issues from CI/CD diagnostic data?

Template-based issue creation transforms diagnostic reports into GitHub issues with proper labels, linked PRs, and commit references. The skill searches existing issues to avoid duplication and enriches new issues with extracted evidence, logs, and suggested fixes.

Does this work for PR validation, merge queues, and trunk deployments?

Yes. The skill applies to workflow-level and job-level errors across PR validation, pre-merge merge-queue runs, trunk deployments, and nightly builds, handling both syntax issues and runtime failures with consistent diagnostic methodology.