analyze-test-run

Download GitHub Actions artifacts and parse junit.xml to summarize integration test outcomes.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/iinoshirozheng/SinoCloudChat --skill analyze-test-run
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: analyze-test-run
Source: https://github.com/iinoshirozheng/SinoCloudChat/tree/main/.agents/skills/analyze-test-run
Command: npx skills add https://github.com/iinoshirozheng/SinoCloudChat --skill analyze-test-run

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzing GitHub Actions test runs can be time consuming; this skill automates extracting artifacts, summarizing results, and surfacing root-cause issues for failures.

Core Features & Use Cases

  • Download artifacts from a GitHub Actions test run and generate a concise skill report.
  • Compute skill invocation rates and compare two runs to spot regressions.
  • File GitHub issues for test failures with root-cause analysis to accelerate remediation.

Quick Start

Run the analyze-test-run skill with a Run ID or URL to generate a structured failure-analysis report.

Frequently Asked Questions about analyze-test-run

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

FAQPage Schema
How do I analyze GitHub Actions test runs and extract junit.xml results?

You can analyze GitHub Actions test runs by providing a Run ID or URL to download artifacts, parse junit.xml, and extract per-test results. This process automatically summarizes outcomes and surfaces failure root causes for integration tests like azure-deploy.

What is the best way to find the root cause of integration test failures in GitHub Actions?

The best way to find the root cause of integration test failures is to download test run artifacts, parse junit.xml, and extract per-test results to produce a structured report. This identifies failure patterns and computes skill invocation rates to pinpoint issues.

Can I compare two GitHub Actions test runs to spot regressions?

You can compare two GitHub Actions test runs to spot regressions by computing skill invocation rates and extracting per-test results. This comparison highlights performance changes and new failures across the selected runs.

Does this approach to test run analysis support downloading SKILL-REPORT.md and agent-metadata files?

This test run analysis approach supports downloading SKILL-REPORT.md and agent-metadata-*.md files alongside junit.xml. It fetches these artifacts from GitHub Actions to generate a comprehensive structured skill report suitable for automated review.

How do I file GitHub issues for test failures with root-cause analysis?

You file GitHub issues for test failures with root-cause analysis by generating a structured skill report from downloaded artifacts and parsed junit.xml results. This report accelerates remediation by providing actionable failure insights directly in the issue.