Diagnose CircleCI failures using Datadog test visibility data.
npx skills add https://github.com/rwc9u/claude-config --skill debug-ci-failure-rwc9u
Please help me install this Agent Skill. Skill: debug-ci-failure Source: https://github.com/rwc9u/claude-config/tree/main/skills/debug-ci-failure Command: npx skills add https://github.com/rwc9u/claude-config --skill debug-ci-failure-rwc9u
Investigate CI failures by bridging CircleCI pipeline data with Datadog CI Test Visibility to surface root causes and accelerate remediation.
Provide a failing CircleCI pipeline URL or PR link and I will fetch the related test results and logs to start debugging.
High-intent search queries and answers about installing and using this skill.
To debug a failing CircleCI pipeline, provide the pipeline URL or PR link to fetch CircleCI metadata and bridge it with Datadog test visibility results, tracing failures from failing specs to logs and traces.
Yes, you can diagnose flaky tests and duration irregularities by analyzing Datadog test events and CircleCI pipeline data to distinguish actual failures from CI-queue timeouts.
You need the CircleCI MCP and Datadog MCP configured to extract failure logs and test results, enabling structured failure context collection across PR checks and branch failures.
The best way to trace a failing spec is bridging CircleCI pipeline metadata with Datadog CI Test Visibility, which surfaces test events and traces to quickly locate the root cause.
Yes, this approach applies to PRs, branch failures, flaky tests, and slow tests across CircleCI pipelines, collecting test events and traces to provide structured failure context for remediation.
huivrotikiTrigger CircleCI pipelines, monitor workflows, and retrieve artifacts via Rube MCP.
AmidVoshakulAnalyze stack traces to isolate failure points and propose code fixes.
luokai25Develop test automation frameworks, scripts, and CI/CD pipeline integrations.
robertolopezlopezRetrieve and inspect CircleCI pipeline, workflow, and job metadata via API v2.
