- Home
- Skills
- DevOps & Cloud
- ci pipeline diagnosis
Works with the AI Agents you already use
ci pipeline diagnosis
- **Metric Computation** generates hard data on failure rates and build reliability without manual spreadsheet work.
$1.99
ci pipeline diagnosis
Example session with this skill installed
Analyze these last 20 pipeline runs from GitHub Actions. Several builds failed during the integration-test step but others passed. I need to know if it is a bottleneck or just flaky.
- Read your context and instructions
- Compiled the ci pipeline diagnosis
The diagnostic script has completed the analysis of 20 pipeline runs. It identified a high failure rate in the integration-test step and clustered three distinct error patterns.
CI Pipeline Diagnosis — Engineering Team, 2023-10-24
1. Summary
- Total Runs: 20
- Success Rate: 65% (13/20)
- Failure Rate: 35% (7/20)
- Bottlenecks Found:
integration-test(p90: 450s) - Flaky Steps Found:
integration-test,lint-check
2. Step Analysis
| Step Name | Executions | Failures | Rate | Mean Dur. | p90 Dur. | Flags |
|---|---|---|---|---|---|---|
| build-assets | 20 | 0 | 0% | 45s | 52s | |
| lint-check | 20 | 2 | 10% | 12s | 15s | FLAKY |
| integration-test | 20 | 5 | 25% | 310s | 450s | BTLNK, FLAKY |
3. Error Clusters
- Pattern A (3 occurrences):
ETIMEDOUT: connection refused to database:5432. Affected steps:integration-test. - Pattern B (2 occurrences):
Error: Process completed with exit code 137. Affected steps:integration-test. - Pattern C (2 occurrences):
Trailing whitespace detected. Affected steps:lint-check.
4. Findings
- High-Impact Flakiness:
integration-testshows non-deterministic failures related to database timeouts.
Resource Constraint: Exit code 137 (OOM) suggests the test runner is running out of memory during heavy integration cycles.
5. Warnings and Data Quality
W002: Missing duration data for 1 run insetup-env.
6. Recommendations and Items for Human Review
- Increase memory limits for the integration-test runner.
- Implement a retry mechanism for database connections in the test suite.
- Management decision required for infrastructure resource allocation.
Next steps
- Review the database connection timeout settings in the integration test config.
- Monitor memory usage on CI runners during the
integration-teststep. - Check
lint-checklocal pre-commit hooks to eliminate simple failures.
Connects securely to your tools. The creator never sees your data.
About this skill
CI pipelines often fail for reasons that aren't immediately obvious, such as transient flakiness, silent bottlenecks, or recurring error patterns across multiple runs. This skill analyzes historical pipeline data to surface exactly where builds are breaking and why.
What it does
- Failure Analysis clusters similar error messages across multiple runs to identify root causes instead of individual symptoms.
- Flakiness Detection identifies steps that fail inconsistently to help isolate non-deterministic tests or environment issues.
- Bottleneck Identification calculates mean and p90 durations for every step to pinpoint which parts of the CI cycle delay development.
- Metric Computation generates hard data on failure rates and build reliability without manual spreadsheet work.
- Prioritized Diagnostics produces a structured report ranking issues by impact with specific recommendations for remediation.
How it works
- Provide pipeline run data, such as exported logs or CI platform JSON exports containing step names, statuses, and durations.
- The agent extracts this data into a structured format for the internal diagnostic engine.
- A deterministic script processes the runs to calculate reliability metrics and cluster errors.
- You receive a formatted Markdown report detailing the findings, error clusters, and prioritized items for review.
Frameworks & tools
This skill is framework-agnostic and works with data from GitHub Actions, GitLab CI, Jenkins, CircleCI, or any system that exports step-level status and duration data.
Why this beats prompting it yourself
Standard LLM prompts often hallucinate performance metrics or miss subtle patterns in large log files. This skill uses a deterministic execution script to ensure failure rates and p90 durations are mathematically accurate while the agent handles the complex task of clustering unstructured error text.
Use cases
- Identify which tests are flaky vs. consistently failing.
- Pinpoint why CI times have increased over the last month.
- Group 100+ failed runs into 3-4 distinct root cause clusters.
- Generate a reliability report for a team lead or engineering manager.
Known limitations
This tool is for historical diagnostic analysis only. It does not provide real-time monitoring, automatic pipeline fixes, or log parsing beyond structured error messages.
Does not perform automatic fixes or real-time monitoring. Limited to historical run data analysis. Requires structured step data (status, duration, error) to function accurately.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 1 day ago