ci-health-report

Analyze Jenkins CI/CD build failures and metrics into an HTML health report.

4|Updated Feb 23, 2026
One-click install
npx skills add https://github.com/npow/claude-skills --skill ci-health-report
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ci-health-report
Source: https://github.com/npow/claude-skills/tree/main/ci-health-report
Command: npx skills add https://github.com/npow/claude-skills --skill ci-health-report

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns scattered CI/CD failures, flaky tests, and build metrics into an actionable health report with verified root causes and prioritized patterns.

Core Features & Use Cases

  • Build Health Analysis: Discovers Jenkins jobs, reviews recent builds, and calculates build counts, success rates, failure rates, and duration statistics.
  • Root-Cause Grouping: Fetches logs for every failed build, extracts concrete errors, groups repeated failures, and distinguishes flaky jobs from broken jobs.
  • Actionable Delivery: Links failures to pull requests and Jenkins builds, includes log evidence, and delivers a concise HTML report suitable for team communication.
  • Use Case: Generate a weekly report showing which tests or infrastructure issues caused CI failures across active repositories, including affected pull requests and recommended patterns for follow-up.

Quick Start

Use the ci-health-report skill to analyze Jenkins builds from the last seven days and produce an HTML CI health report for the configured repositories.

Frequently Asked Questions about ci-health-report

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a CI health report from Jenkins build failures?

To generate a CI health report, the Skill analyzes Jenkins build failures and metrics over a specified period, verifies root causes, and delivers a concise HTML report with grouped log evidence and affected pull requests.

Can I identify flaky tests and root causes from Jenkins build logs?

You can identify flaky tests by analyzing CI/CD build logs to extract concrete errors, group repeated failures, and distinguish flaky jobs from persistently broken jobs using deterministic failure classification.

Do I need configured CI MCP access to analyze build success rates?

Yes, you need configured CI MCP access to retrieve build-log resources, resolve pull request context, and calculate build success rates, failure rates, and duration statistics across Jenkins repositories.

What is included in an actionable CI/CD build health report?

This Skill links Jenkins build failures to their corresponding pull requests and includes concrete log evidence within an HTML report, making it suitable for direct team communication and follow-up.

Does this Skill work with Jenkins controllers to investigate recurring infrastructure issues?

Yes, this Skill applies to Jenkins controllers and repositories to investigate recurring infrastructure or test issues by fetching logs for every failed build and grouping repeated failures for actionable insights.

What format is the CI health report delivered in?

The Skill produces an HTML CI health report containing build counts, success rates, failure rates, duration statistics, verified root causes, and recommended patterns for team follow-up.