rca:ci

Analyzes CI pipeline logs and artifacts to identify root causes of failures.

292|103|Updated Mar 27, 2025
One-click install
npx skills add https://github.com/kagenti/kagenti --skill rca-ci
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: rca:ci
Source: https://github.com/kagenti/kagenti/tree/main/.claude/skills/rca%3Aci
Command: npx skills add https://github.com/kagenti/kagenti --skill rca-ci

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides a systematic approach to identifying the root cause of failures in Continuous Integration (CI) pipelines when only CI logs and artifacts are available.

Core Features & Use Cases

  • Log Analysis: Efficiently parses CI logs to pinpoint errors and failure points.
  • Artifact Inspection: Downloads and analyzes CI artifacts for deeper insights into failures.
  • Hypothesis Generation: Helps in forming and verifying hypotheses about the cause of the failure.
  • Use Case: A CI build fails unexpectedly. You use rca:ci to analyze the logs, identify the specific test that failed, understand the error message, and hypothesize that a recent configuration change is the likely culprit.

Quick Start

Use the rca:ci skill to analyze the logs from the most recent failed CI run.

Frequently Asked Questions about rca:ci

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

FAQPage Schema
How do I find the root cause of a CI pipeline failure from logs?▼

To find the root cause of a CI pipeline failure, you can systematically analyze available CI logs and artifacts to isolate errors, hypothesize causes based on categories like timing or configuration, and verify them through log pattern matching.

What types of CI failures can be diagnosed through log analysis?▼

Log analysis can diagnose CI failures by hypothesizing causes across common categories like timing, configuration, authentication, network, state, and resource issues, then verifying them through pattern matching and cross-referencing previous runs.

Do I need live cluster access to troubleshoot CI failures?▼

You do not need live cluster access to troubleshoot CI failures initially. The skill performs root cause analysis using only available logs and artifacts, escalating to rca:hypershift only when live cluster access is required.

How do I analyze CI artifacts to troubleshoot an unexpected build failure?▼

You can analyze CI artifacts by downloading and inspecting them alongside CI logs to pinpoint specific error points, form hypotheses about recent configuration changes, and systematically verify the root cause.

Does the root cause analysis process check for security vulnerabilities?▼

The root cause analysis process checks for CVEs before documenting findings, ensuring that identified security vulnerabilities are reviewed as part of the final troubleshooting output.