Analyzes CircleCI failures to identify flakiness versus genuine bugs.
Install
mkdir -p .claude/skills/circleci-why-flaky && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/12468" && unzip -o skill.zip -d .claude/skills/circleci-why-flaky && rm skill.zipInstalls to .claude/skills/circleci-why-flaky
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.
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.Key capabilities
- →Classify recent CircleCI workflow failures
- →Identify fixable flake, external outages, and real bugs
- →Fetch CircleCI workflow and job logs
- →Discover failure patterns using `grep`
- →Generate a summary report of failure categories
- →Determine if retrying CI is effective
How it works
The skill fetches CircleCI workflow and job logs, then guides the user through an iterative pattern discovery process using `grep` to classify failures into categories like fixable flake, external outage, or real bug. It generates a summary report.
Inputs & outputs
When to use circleci-why-flaky
- →Debug CI flakiness
- →Identify why CI failed
- →Analyze workflow failure trends
About circleci-why-flaky
Fetches and analyzes recent CircleCI logs to bucketize failure causes, helping developers determine if retrying is an effective fix.
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.
When not to use it
- →When the user needs to reimplement fetching logic
- →When the user needs to analyze every job upfront
Limitations
- →Requires `grep` for pattern discovery
- →Output directory must be specified with `--out`
- →Relies on `~/.circleci/cli.yml` for authentication or explicit token
How it compares
This skill provides a structured, iterative method for classifying CircleCI failures, helping to distinguish between transient issues and actual bugs, unlike simply reviewing raw logs.
Compared to similar skills
circleci-why-flaky side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| circleci-why-flaky (this skill) | 0 | 3mo | Review | Intermediate |
| cicd-diagnostics | 1 | 6mo | Review | Advanced |
| posthog-ci-integration | 1 | 2mo | Caution | Intermediate |
| verification-quality-assurance | 1 | 4mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
cicd-diagnostics
dotCMS
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".
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.
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.