| name | ci-cd-reporter |
| description | Turn raw CI/CD pipeline output into a readable report. Use when the user pastes build/pipeline logs or asks to summarize CI results. |
CI/CD Reporter
Analyze CI/CD pipeline outputs and generate human-readable test/build reports.
Description
This skill transforms raw CI/CD pipeline outputs (test results, build logs, coverage reports) into clear, actionable reports. It parses JUnit XML, coverage data, build logs, and deployment outputs to give teams a quick understanding of pipeline health.
Instructions
When the user provides CI/CD output or pipeline results:
- Parse Results: Extract test results, coverage data, and build status from raw output
- Summarize: Create an executive summary of the pipeline run
- Highlight Failures: Detail any failures with context and likely causes
- Trend Analysis: If historical data is available, identify trends
- Action Items: Recommend next steps based on results
Supported Inputs
Test Results
- JUnit/xUnit XML reports
- Jest/Mocha JSON output
- pytest output (verbose or JUnit XML)
- Raw test runner console output
- Cucumber/BDD report files
Coverage Reports
- Istanbul/NYC JSON or text output
- Coverage.py output
- JaCoCo reports
- lcov data
Build Logs
- GitHub Actions workflow logs
- GitLab CI/CD logs
- Jenkins console output
- Docker build output
- Compilation errors and warnings
Output Format
# Pipeline Report
**Pipeline**: [name]
**Run**: #[number]
**Branch**: [branch]
**Commit**: [sha]
**Date**: [timestamp]
**Duration**: [time]
## Status: PASS / FAIL
## Summary
| Metric | Value | Threshold | Status |
|--------|-------|-----------|--------|
| Tests Passed | X/Y | 100% | OK/FAIL |
| Code Coverage | X% | 80% | OK/FAIL |
| Build Time | Xs | <300s | OK/FAIL |
| Lint Errors | X | 0 | OK/FAIL |
## Failed Tests (X)
### test_name
- **File**: [path]
- **Error**: [message]
- **Expected**: [value]
- **Actual**: [value]
- **Likely Cause**: [analysis]
## Coverage Breakdown
| Module | Statements | Branches | Functions | Lines |
|--------|-----------|----------|-----------|-------|
## Uncovered Critical Paths
- [file:line] - [description of uncovered code]
## Recommendations
1. [Prioritized action items]
## Flaky Test Candidates
- [Tests that passed/failed inconsistently]
Smart Analysis
- Identifies tests that seem flaky (different results across runs)
- Flags coverage decreases in critical modules
- Highlights build time regressions
- Detects dependency-related failures
- Groups related test failures by root cause
Example Usage
Parse this JUnit XML and give me a summary of what failed and why:
[paste XML]
Here's the GitHub Actions output for our failing pipeline. What went wrong?
[paste log]
