How does the CI Failure Analyzer access my repositories?

It utilizes your existing GitHub CLI authentication or a provided GH_TOKEN environment variable to securely access and read job logs.

Is there a way to monitor the AI usage for this skill?

Yes, by appending the --debug flag to your command, you can view detailed token counts and estimated costs for the analysis.

Does this skill work with CI providers other than GitHub Actions?

Currently, this skill is specifically optimized for GitHub Actions logs and GitHub Pull Request structures.

What information is included in the failure summary?

The analysis provides a root cause explanation, specific error messages, names of failing tests, and the most relevant snippets from the log files.

Can I analyze specific jobs instead of an entire pull request?

Yes, you can pass individual GitHub Action job URLs directly to the skill for targeted analysis of a specific failure.

CI Failure Analyzer

Name: CI Failure Analyzer
Author: mlflow

bymlflow

0•

Deployment & DevOps

Analyzes failed GitHub Action jobs to provide concise root-cause summaries and actionable insights.

This skill automates the tedious process of debugging CI/CD pipelines by scanning logs from failed GitHub Action jobs. Using Claude's reasoning capabilities, it extracts relevant error messages, identifies failing tests, and provides a clear summary of why a build failed, helping developers fix integration issues faster without manually sifting through thousands of lines of logs. It supports both full pull request analysis and targeted individual job debugging.