ci-failure-analysis

Diagnose failed GitHub Actions CI/CD runs for Breenix kernel development.

7|Updated Nov 21, 2015
One-click install
npx skills add https://github.com/ryanbreen/breenix --skill ci-failure-analysis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ci-failure-analysis
Source: https://github.com/ryanbreen/breenix/tree/main/breenix-ci-failure-analysis
Command: npx skills add https://github.com/ryanbreen/breenix --skill ci-failure-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

CI/CD failures in kernel development are complex and time-consuming to diagnose. This Skill automates the identification of common failure patterns, reducing manual log analysis and speeding up root cause determination.

Core Features & Use Cases

  • Automated Pattern Detection: Automatically identifies common kernel CI failures like double faults, page faults, test timeouts, and environment issues.
  • Contextual Diagnosis: Provides immediate diagnosis and suggested fixes for detected problems, complete with relevant log context.
  • Use Case: A GitHub Actions workflow for your Breenix kernel fails. Instead of manually sifting through thousands of log lines, use this Skill to instantly pinpoint the exact error (e.g., a page fault at a specific address) and get actionable steps to resolve it.

Quick Start

Analyze a CI log file

ci-failure-analysis/scripts/analyze_ci_failure.py target/xtask_ring3_smoke_output.txt

Show context around failures

ci-failure-analysis/scripts/analyze_ci_failure.py --context target/xtask_ring3_smoke_output.txt

Frequently Asked Questions about ci-failure-analysis

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

FAQPage Schema
How do I diagnose GitHub Actions CI failures in kernel development?

Diagnose CI failures by analyzing GitHub Actions logs for common kernel patterns like double faults, page faults, and timeouts. This Skill automatically detects failure signatures, extracts contextual evidence, and provides structured diagnosis with remediation steps to accelerate root cause identification.

Can I analyze QEMU and kernel panic logs to find the root cause?

Yes. This Skill analyzes QEMU/KVM kernel logs and identifies patterns including kernel panics, page faults at specific addresses, and environment issues. It extracts relevant log context and delivers actionable diagnostic output pinpointing the exact failure.

What CI failure patterns does automated log analysis detect?

Automated pattern detection identifies double faults, page faults, test timeouts, QEMU not found, missing Rust targets, missing rust-src, userspace binary errors, compilation failures, signal issues, and kernel panics—reducing manual log sifting in CI workflows.

How do I extract context around CI log failures quickly?

Use the context flag to display surrounding log lines around detected failures. This surfaces relevant kernel state, environment variables, and system output needed to understand failure conditions without manually searching thousands of log entries.

Does this work with environment-related CI timeouts and missing dependencies?

Yes. The Skill diagnoses environment issues including timeouts, missing dependencies like Rust targets or rust-src, and QEMU unavailability. It identifies these blockers and recommends corrective steps for CI workflow resumption.

What's the fastest way to reduce kernel CI debugging time?

Automate failure pattern detection on CI logs to skip manual analysis. This Skill instantly categorizes failures, pinpoints root causes with log evidence, and supplies remediation guidance—eliminating hours of log review per failure.