skills.rest
dotnet
dotnetOFFICIAL
Explore all skills by this author →
Website𝕏@dotnetfdnGitHub

helix-investigation

Diagnose Helix test failures by collecting AzDO timelines, job data, and console logs.

13|20|Updated Mar 10, 2026
Search Tags:#root-cause#log-analysis#failure-analysis#ci-pipeline#helix#azdo
One-click install
npx skills add https://github.com/dotnet/arcade-skills --skill helix-investigation
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: helix-investigation
Source: https://github.com/dotnet/arcade-skills/tree/main/plugins/dotnet-dnceng/skills/helix-investigation
Command: npx skills add https://github.com/dotnet/arcade-skills --skill helix-investigation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Helix test investigations often require piecing together AzDO timelines, Helix job data, and raw console logs to identify why a pipeline fails. This skill provides a structured approach to collect these signals and surface root-cause patterns for faster remediation.

Core Features & Use Cases

  • Enumerates Helix work items for a given job to surface test groups, machine names, and exit codes.
  • Downloads console logs and test results to enable side-by-side failure analysis across multiple runs.
  • Distills findings into actionable root-cause categories (machine-specific, device/infrastructure, or systemic) with recommended next steps.
  • Use Case: identify whether a failing test is tied to a specific machine, queue, or Helix configuration, and guide issue filing.

Quick Start

Provide an AzDO build URL and the corresponding Helix job to begin collecting logs and generating root-cause insights.

Frequently Asked Questions about helix-investigation

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

FAQPage Schema
How do I diagnose Helix test failures in Azure DevOps pipelines?▼

Diagnose Helix test failures by collecting AzDO timelines, Helix job data, and raw console logs to compare failing versus passing runs and surface root-cause patterns for faster remediation.

What is the best way to find root causes for Helix pipeline failures across Apple, Android, and Windows queues?▼

Finding root causes for Helix pipeline failures involves enumerating Helix work items to surface machine names and exit codes, then categorizing issues as machine-specific, infrastructure-related, or systemic.

Do I need AzDO access and Helix MCP tools to investigate Helix job data?▼

Yes, investigating Helix job data requires AzDO access, Helix MCP tools, and curl to fetch raw console logs and test results necessary for root-cause analysis.

How do I categorize Helix test failures as machine-specific or systemic?▼

Categorize Helix test failures by comparing failing versus passing runs to identify patterns, then distill findings into actionable root-cause categories with recommended next steps for issue filing.

Why does my Helix test fail on a specific machine or queue configuration?▼

Helix tests may fail on specific machines or queues due to device or infrastructure issues; enumerating work items and analyzing exit codes helps determine if the failure is tied to a particular machine or systemic.

Related Skills

Explore More Software Engineering Skills→
dotnetdotnet
13

pipeline-investigation

Identify and analyze Azure DevOps pipeline failures outside Helix to determine root causes.

Official
Intermediate
cc01cccc01cc
4

bug-root-cause-structurer

Produces structured bug root-cause analyses with actionable repair plans and verification steps.

Community
Advanced
dotnetdotnet
23.3k

run-helix-tests

Automate submission and monitoring of MAUI unit tests on Helix queues across Windows and macOS platforms.

Official
Intermediate
lewinglewing
4

ci-analysis

Analyze Azure DevOps and Helix CI failures for dotnet repository PRs.

Community
Advanced