analyze-test-run

Name: analyze-test-run
Author: microsoft

Analyze a GitHub Actions integration test run and produce a skill invocation report with failure root-cause issues. TRIGGERS: analyze test run, skill invocation rate, test run report, compare test runs, skill invocation summary, test failure analysis, run report, test results, action run report

Stars

★ 232

Source

GitHub

Updated

2026-07-13

// securityLow risk

Prompt only, no code
Open source
Community-trusted· 232

Running security audit…

Credentials
Network egress
Code execution
Data access
Supply chain

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "analyze-test-run" skill from askskill:
1. Download https://raw.githubusercontent.com/microsoft/GitHub-Copilot-for-Azure/main/.github/skills/analyze-test-run/SKILL.md
2. Save it as ~/.claude/skills/analyze-test-run/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

Analyze Test Run

Downloads artifacts from a GitHub Actions integration test run, generates a summarized skill invocation report, and files GitHub issues for each test failure with root-cause analysis.

When to Use

Summarize results of a GitHub Actions integration test run
Calculate skill invocation rates for the skill under test
For azure-deploy tests: track the full deployment chain (azure-prepare → azure-validate → azure-deploy)
Compare skill invocation across two runs
File issues for test failures with root-cause context

Input

Parameter	Required	Description
Run ID or URL	Yes	GitHub Actions run ID (e.g. `22373768875`) or full URL
Comparison Run	No	Second run ID/URL for side-by-side comparison

MCP Tools

All tools use owner: "microsoft" and repo: "GitHub-Copilot-for-Azure" as fixed parameters. method selects the operation within the tool.

Tool	`method`	Key Parameter	Purpose
`actions_get`	`get_workflow_run`	`resource_id`: run ID	Fetch run status and metadata
`actions_list`	`list_workflow_run_artifacts`	`resource_id`: run ID	List all artifacts for a run
`actions_get`	`download_workflow_run_artifact`	`resource_id`: artifact ID	Get a temporary download URL for an artifact ZIP
`get_job_logs`	—	`run_id` + `failed_only: true`	Retrieve job logs when artifact content is inaccessible
`search_issues`	—	`query`: search string	Find existing open issues before creating new ones
`create_issue`	—	`title`, `body`, `labels`, `assignees`	File a new GitHub issue for a test failure

Workflow

Phase 1 — Download & Parse

Extract the numeric run ID from the input (strip URL prefix if needed)

Fetch run metadata using the MCP actions_get tool:

actions_get({ method: "get_workflow_run", owner: "microsoft", repo: "GitHub-Copilot-for-Azure", resource_id: "<run-id>" })

List artifacts using the MCP actions_list tool, then download each relevant artifact:
```
// List artifacts
actions_list({ method: "list_workflow_run_artifacts", owner: "microsoft", repo: "GitHub-Copilot-for-Azure", resource_id: "<run-id>" })
// Download individual artifacts by ID
actions_get({ method: "download_workflow_run_artifact", owner: "microsoft", repo: "GitHub-Copilot-for-Azure", resource_id: "<artifact-id>" })
```
The download returns a temporary URL. Fetch the ZIP archive from that URL and extract it locally. If the environment restricts outbound HTTP (e.g. AWF sandbox), record in the analysis report that artifact content was unavailable and fall back to job logs via the get_job_logs MCP tool.
Locate these files in the downloaded artifacts:
- junit.xml — test pass/fail/skip/error results
- *-SKILL-REPORT.md — generated skill report with per-test details
- agent-metadata-*.md files — raw agent session logs per test
⚠️ Note: If artifact ZIP files cannot be downloaded due to network restrictions, or if downloaded files cannot be extracted, use the get_job_logs MCP tool to identify test failures and produce a best-effort analysis from whatever data is accessible.

Phase 2 — Build Summary Report

Produce a markdown report with four sections. See report-format.md for the exact template.

Section 1 — Test Results Overview

Parse junit.xml to build:

Metric	Value
Total tests	count from `<testsuites tests=…>`
Executed	total − skipped
Skipped	count of `<skipped/>` elements
Passed	executed − failures − errors
Failed	count of `<failure>` elements
Test Pass Rate	passed / executed as %

Include a per-test table with name, duration (from time attribute, convert seconds to Xm Ys), and Pass/Fail result.

Section 2 — Skill Invocation Rate

…

View full docs ↗

microsoftGet→

$ loading_