ci-test-failures Skill

Source

• Creator: microsoft
• Repository: microsoft/aspire
• Skill file: .agents/skills/ci-test-failures/SKILL.md

What it does

Guide for diagnosing GitHub Actions test failures, extracting failed tests from runs, and creating or updating failing-test issues. Use this when asked to investigate GitHub Actions test failures, download failure logs, create failing-test issues, or debug CI issues.

Skill instructions

CI Test Failure Diagnosis and Issue Filing Recipe: Create an Issue for a Test Failure When the user asks to create an issue for a failing test, follow these steps. Always redirect full output to a log file (not tail) so you can inspect it if the command fails. Step 1: List failed tests (if user didn't specify one) Omit --test to discover all failures. Redirect output to a log file: bash dotnet run --project tools/CreateFailingTestIssue -- \ --url "<the-url-the-user-gave" \ --output /tmp/cfti-result.json \ /tmp/cfti-list.log 2&1 powershell dotnet run --project tools/CreateFailingTestIssue -- --url "<the-url-the-user-gave" --output $env:TEMP/cfti-result.json $env:TEMP/cfti-list.log 2&1 Then read the result with jq: bash jq '{ success, availableFailedTests: .diagnostics.availableFailedTests, errorMessage: .errorMessage }' /tmp/cfti-result.json powershell Get-Content $env:TEMP/cfti-result.json | ConvertFrom-Json | Select-Object success, errorMessage, @{N='availableFailedTests';E={$.diagnos