skills.rest
tony-adm
tony-admCOMMUNITY
Explore all skills by this author →
GitHub

cicd-diagnostics

Diagnose DotCMS GitHub Actions CI/CD failures with log analysis and root-cause classification.

Updated Aug 23, 2026
Search Tags:#automation#diagnostics#github-actions#ci-cd#root-cause#log-analysis
One-click install
npx skills add https://github.com/tony-adm/dotCMSdocker --skill cicd-diagnostics-tony-adm
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cicd-diagnostics
Source: https://github.com/tony-adm/dotCMSdocker/tree/main/.claude/skills/cicd-diagnostics
Command: npx skills add https://github.com/tony-adm/dotCMSdocker --skill cicd-diagnostics-tony-adm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides AI-guided diagnostics for DotCMS CI/CD failures across GitHub Actions workflows, enabling rapid triage, root-cause analysis, and actionable remediation recommendations.

Core Features & Use Cases

  • Progressive log analysis and streaming search to handle large CI/CD logs
  • Tiered evidence extraction (Level 1 summary, Level 2 details, Level 3 full context)
  • Root-cause classification (new vs. flaky vs. infrastructure)
  • Cross-workflow comparison (PR vs. merge-queue vs. nightly)
  • GitHub issue creation with structured templates and labels

Quick Start

  1. Initialize a diagnostic workspace for a given run
  2. Fetch workflow metadata and failed job logs with the standardized parameter order
  3. Generate tiered extractions and a natural-diagnosis report, then decide on issue creation if needed

Frequently Asked Questions about cicd-diagnostics

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

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

CI/CD failure diagnosis involves analyzing workflow logs and job metadata to identify root causes. This Skill automates that process by extracting evidence from GitHub Actions runs, classifying failures as new, flaky, or infrastructure-related, and generating actionable remediation guidance with cross-run comparisons.

Can I analyze large CI/CD logs efficiently without manual review?▼

Progressive log analysis with streaming search handles large CI/CD logs by extracting tiered evidence—summary, detailed findings, and full context—so you pinpoint failures without reviewing entire logs manually.

How do I compare CI/CD failures across different workflow types?▼

Cross-workflow comparison enables you to identify patterns by analyzing PR validation, merge-queue validation, trunk deployments, and nightly builds side-by-side, distinguishing between environment-specific, code-specific, and systemic failures.

What's the fastest way to triage and document CI/CD failures?▼

Automated GitHub issue creation with structured templates and labels reduces triage time by capturing diagnostic findings directly into tracked issues, enabling team coordination without manual documentation overhead.

Do I need to manually extract CI/CD run metadata and logs?▼

No. Standardized parameter handling and automated metadata extraction retrieve workflow runs, job details, and logs from GitHub Actions in a single workflow, eliminating manual log collection and formatting.

Related Skills

Explore More Software Engineering Skills→
drvossdrvoss
42

actions-debugging

Diagnose failed GitHub Actions workflow runs and identify root causes.

Community
Intermediate
dotnetdotnet
2.9k

macios-ci-postmortem

Classify CI failures from recent dotnet/macios PRs and suggest GitHub issue actions.

Official
Advanced
mymx2mymx2
4

gh-fix-ci

Diagnose failing GitHub Actions CI checks by parsing PR job logs.

Community
Advanced
willyu1007willyu1007

instrument-backend-observability

Instrument backend services with logging, error tracking, metrics, and tracing.

Community
Intermediate