helix-investigation

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.