analyze-ci-failure

Diagnose GitHub Actions workflow failures by inspecting job logs for root causes.

343|68|Updated Jun 14, 2017

Search Tags:#automation #ci/cd #debugging #github actions #android #gradle

Ready to run

npx skills add https://github.com/MartinStyk/AndroidApkAnalyzer --skill analyze-ci-failure

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: analyze-ci-failure
Source: https://github.com/MartinStyk/AndroidApkAnalyzer/tree/main/.claude/skills/analyze-ci-failure
Command: npx skills add https://github.com/MartinStyk/AndroidApkAnalyzer --skill analyze-ci-failure

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the frustration of digging through massive, noisy CI logs by automatically isolating the specific failing step and identifying the root cause of build failures in Android projects.

Core Features & Use Cases

Automated Log Filtering: Uses the GitHub CLI to pull only the failing job logs and filter for critical error signatures like Gradle task failures or compilation exceptions.
Root Cause Analysis: Maps common failure patterns—such as Firebase configuration errors, signing issues, or formatting violations—to actionable fixes.
Use Case: When a pull request fails its CI check, use this Skill to instantly identify if the failure is due to a missing secret, a formatting error, or a compilation issue, and receive a clear path to resolution.

Quick Start

Use the analyze-ci-failure skill to check the latest build for this PR and propose a fix for any errors found.

Frequently Asked Questions about analyze-ci-failure

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

FAQPage Schema

How do I diagnose GitHub Actions failures for Android Gradle builds?▼

To diagnose GitHub Actions failures for Android Gradle builds, you can automatically pull failing job logs using the GitHub CLI to filter for critical error signatures like compilation exceptions and map them to actionable fixes.

Why does my Android CI pipeline fail on Firebase configuration errors?▼

Android CI pipelines often fail on Firebase configuration errors due to missing secrets or invalid setup. Analyzing the specific failing step logs maps these common failure patterns to identify the exact missing configuration.

Do I need the GitHub CLI authenticated to analyze CI logs?▼

Yes, you need the GitHub CLI (gh) authenticated and configured to access repository workflow runs and secret metadata to automatically pull and filter failing job logs for root cause analysis.

What is the best way to find the root cause of a Gradle task failure in CI?▼

The best way to find the root cause of a Gradle task failure in CI is isolating the specific failing step by filtering noisy logs for critical error signatures, which streamlines developer feedback loops.

Can I identify missing GitHub Actions secrets from failed workflow runs?▼

Yes, you can identify missing GitHub Actions secrets from failed workflow runs by inspecting job logs to map common failure patterns, such as signing issues or Firebase errors, to specific missing secret metadata.

How to fix compilation exceptions found in GitHub Actions job logs?▼

To fix compilation exceptions in GitHub Actions job logs, the logs are analyzed to isolate the failing step and identify the root cause, providing a clear path to resolution for the build errors.