skills.rest
microsoft
microsoftOFFICIAL
Explore all skills by this author →
Website𝕏@OpenAtMicrosoftGitHub

ci-test-failures

Diagnose GitHub Actions test failures by extracting failed test names and downloading job logs and artifacts.

6.2k|952|Updated Sep 25, 2023
Search Tags:#github actions#observability#test failures#dotnet#issue creation#test artifacts#ci troubleshooting
One-click install
npx skills add https://github.com/microsoft/aspire --skill ci-test-failures
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ci-test-failures
Source: https://github.com/microsoft/aspire/tree/main/.agents/skills/ci-test-failures
Command: npx skills add https://github.com/microsoft/aspire --skill ci-test-failures

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you quickly understand why GitHub Actions tests failed, locate the specific failing test(s), and create or update the corresponding failing-test issues in a consistent template format.

Core Features & Use Cases

  • Identify failing tests from a run: Lists available failed test names from workflow runs to support one-issue-per-test filing.
  • Download and inspect failure artifacts: Fetches failed job logs and test artifacts (.trx, logs, and related files) to support root-cause investigation.
  • Create/update failing-test issues automatically: Uses the repository’s automation/tooling to generate template-compliant issue content, reuse matching open issues, or reopen closed ones.
  • Supports multiple URL inputs: Works with PR URLs, run URLs, attempt URLs, and job URLs to resolve the correct workflow context.

Quick Start

Run the investigation and then file issues for the specific failing test(s) from your GitHub Actions run URL by executing the CreateFailingTestIssue tool with the URL and a chosen failing test name, writing results to a JSON file for clean parsing.

Frequently Asked Questions about ci-test-failures

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

FAQPage Schema
How do I diagnose GitHub Actions test failures and identify the specific failing test?▼

To diagnose GitHub Actions test failures, you can extract failed test names from a given workflow run and download the corresponding job logs and test artifacts to investigate the root cause of the failing test.

Can I automatically create or update repository issues for failing tests from a CI run?▼

Yes, you can automatically create or update failing-test issues by using the CreateFailingTestIssue tool with your run URL and the selected failing test name, generating template-compliant issue content to reuse or reopen matching issues.

What URL formats are supported when investigating CI test failures in GitHub Actions?▼

When investigating CI test failures, the tool supports resolving the correct workflow context from multiple URL inputs including pull request URLs, run URLs, attempt URLs, and job URLs.

How do I download and inspect test artifacts like .trx files from a GitHub Actions run?▼

You can download and inspect test artifacts by fetching failed job logs and related test files directly from the GitHub Actions run context to support your root-cause investigation.

What is the best way to avoid manually constructing GitHub issues for dotnet test failures?▼

The best way to avoid manual issue construction for dotnet test failures is to execute the CreateFailingTestIssue tool with the run URL and chosen failing test name, writing the output to a JSON file for clean, deterministic parsing.

Does this CI troubleshooting tool reuse existing open issues when filing failing test reports?▼

Yes, during CI troubleshooting, the tool checks the repository's automation to reuse matching open issues or reopen closed ones, ensuring one issue is filed per failing test to maintain a consistent template format.

Related Skills

Explore More Software Engineering Skills→
yiminllinyiminllin
1

debug-phoenix-hil-from-gha

Identify the primary cause of a Phoenix HIL failure in a GitHub Actions job run.

Community
Advanced
KingInYellowsKingInYellows

ce-debug

Diagnose bugs through a phase-based investigation from symptom to root cause.

Official
Advanced
GeneralReasoningGeneralReasoning
4

analyze-ci

Analyze failed GitHub Actions jobs for a pull request and output a failure summary.

Official
Intermediate
golemcloudgolemcloud
1.5k

analysing-ci-failures

Analyze GitHub Actions CI failures from job URLs and CTRF test reports.

Official
Intermediate