ci-test-failures

Diagnose GitHub Actions CI test failures by downloading and analyzing job logs.

Updated Mar 19, 2026

Search Tags:#github actions #github api #ci testing #test debugging #ci issue diagnosis

Ready to run

npx skills add https://github.com/sast-playground/aspire --skill ci-test-failures-sast-playground

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ci-test-failures
Source: https://github.com/sast-playground/aspire/tree/main/.github/skills/ci-test-failures
Command: npx skills add https://github.com/sast-playground/aspire --skill ci-test-failures-sast-playground

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires dotnet, github-cli, python, and includes scripts (resource) and assets (resource) components.

What problem does it solve?

Diagnosing and fixing CI test failures can be a complex and time-consuming task. This skill streamlines the process with the DownloadFailingJobLogs tool.

Core Features & Use Cases

Automated Job Log Downloading: Automatically download job logs and artifacts from GitHub Actions runs.
Log and Artifacts Analysis: Provide structured access to test failures and errors.
Test Artifacts Extraction: Download and extract artifacts containing .trx files and test logs for further analysis.
Error and Timeout Diagnostics: Identify common failure patterns like disk space exhaustion, command not found, and timeout issues.
GitHub API for Annotations: Utilize GitHub API to find errors when job logs are not available.
Use Case: Quickly diagnose and address issues in CI tests when working with the Aspire repository.

Quick Start

Use the ci-test-failures skill to diagnose CI test failures by providing the run ID.

Frequently Asked Questions about ci-test-failures

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

FAQPage Schema

How do I download GitHub Actions job logs and artifacts for failed CI test runs?▼

To diagnose CI test failures and identify common error patterns, the skill analyzes downloaded test artifacts and logs to detect issues like disk space exhaustion, command not found errors, and timeout issues in GitHub Actions workflows.

How do I identify common error patterns like disk space exhaustion or timeouts in GitHub Actions workflows?▼

To identify common error patterns like disk space exhaustion or timeouts in GitHub Actions workflows, the skill analyzes downloaded test artifacts and logs to detect these specific failure signatures automatically.

Do I need the gh CLI to diagnose CI test failures in the Aspire repository?▼

Yes, you need the gh CLI installed and authenticated to diagnose CI test failures in the Aspire repository, because the skill requires GitHub CLI for GitHub API interaction to download logs and retrieve error annotations.

How can I find CI test errors when GitHub Actions job logs are not available?▼

To find CI test errors when GitHub Actions job logs are not available, the skill utilizes the GitHub API to fetch and analyze error annotations directly, ensuring failure diagnosis can proceed without standard log files.

What dependencies are required to run Python scripts for CI issue diagnosis?▼

To run Python scripts for CI issue diagnosis, the required dependencies include dotnet, github-cli, and python, ensuring the environment can interact with GitHub APIs and extract .trx test artifacts successfully.