Diagnoses CI/CD failures in dotCMS projects by triaging build logs and known issues.
Install
mkdir -p .claude/skills/cicd-diagnostics && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/4133" && unzip -o skill.zip -d .claude/skills/cicd-diagnostics && rm skill.zipInstalls to .claude/skills/cicd-diagnostics
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Use when a GitHub Actions workflow fails, PR build breaks, merge queue rejects, nightly reports failures, or user mentions CI/CD test failures in dotCMS/core. Also use for "check build", "diagnose run", "why did CI fail", "flaky test", "merge queue blocked".Key capabilities
- →Executes pre-flight checks for DotCMS CI/CD environment integrity
- →Analyzes historical workflow run logs to identify failure patterns
- →Distinguishes between test assertion errors and infrastructure failures
- →Correlates build failures with known flaky test datasets
How it works
Runs specialized diagnostic Python scripts that parse CI logs and cross-reference failure patterns against a known issues database.
Inputs & outputs
When to use cicd-diagnostics
- →Triaging PR build failures
- →Analyzing merge queue blocks
- →Debugging flaky test suites
- →Investigating CI/CD infrastructure
About cicd-diagnostics
Uses specialized diagnostic scripts to analyze GitHub Actions failures. It prioritizes checking known issues and flaky tests to reduce debugging time for platform engineers.
Diagnoses DotCMS GitHub Actions failures (PR builds, merge queue, nightly, trunk). Analyzes failed tests, root causes, compares runs. Use for "fails in GitHub", "merge queue failure", "PR build failed", "nightly build issue".
When not to use it
- →Projects outside of the dotCMS/core repository
- →General non-CI/CD related debugging tasks
Prerequisites
Limitations
- →Strictly bound to DotCMS/core infrastructure
- →Limited by the quality and availability of historical log data
How it compares
Prevents redundant deep dives into source code by prioritizing triage and known-issue lookup for standard CI/CD infrastructure.
Compared to similar skills
cicd-diagnostics side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| cicd-diagnostics (this skill) | 1 | 4mo | Review | Advanced |
| posthog-ci-integration | 1 | 27d | Caution | Intermediate |
| verification-quality-assurance | 1 | 3mo | Review | Intermediate |
| circleci-why-flaky | 0 | 1mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by dotCMS
View all by dotCMS →You might also like
posthog-ci-integration
jeremylongshore
Configure PostHog CI/CD integration with GitHub Actions and testing. Use when setting up automated testing, configuring CI pipelines, or integrating PostHog tests into your build process. Trigger with phrases like "posthog CI", "posthog GitHub Actions", "posthog automated tests", "CI posthog".
verification-quality-assurance
ruvnet
Comprehensive truth scoring, code quality verification, and automatic rollback system with 0.95 accuracy threshold for ensuring high-quality agent outputs and codebase reliability.
circleci-why-flaky
mui
Classify recent CircleCI workflow failures into buckets so you can see what's flake vs what's a real bug. Use when CI on a branch is failing repeatedly and you want to know whether retries will fix it. Infers project + branch from the current git repo; defaults to last 7 days.
regression-testing
upex-galaxy
Execute regression test suites via CI/CD, analyze results, classify failures, and produce GO/NO-GO release decisions. Use when running regression, smoke, or sanity suites through GitHub Actions, monitoring workflow runs, downloading Allure or Playwright artifacts, classifying failures (REGRESSION vs
ci
PioneersHub
Run the local CI pipeline (ruff, bandit, pytest, sonar-scanner) and refresh SonarQube.
qa-tester
svilupp
Browser automation QA testing skill. Systematically tests web applications for functionality, security, and usability issues. Reports findings by severity (CRITICAL/HIGH/MEDIUM/LOW) with immediate alerts for critical failures.