ci-analysis

Analyze Azure DevOps and Helix CI build and test failures for .NET pull requests.

3|Updated Feb 6, 2026

Search Tags:#testing #debugging #troubleshooting #azure devops #ci #helix

Ready to run

npx skills add https://github.com/ilonatommy/copilot-skills --skill ci-analysis-ilonatommy

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ci-analysis
Source: https://github.com/ilonatommy/copilot-skills/tree/main/runtime-skills/ci-analysis
Command: npx skills add https://github.com/ilonatommy/copilot-skills --skill ci-analysis-ilonatommy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps you quickly understand and diagnose why Continuous Integration (CI) builds are failing, saving valuable debugging time.

Core Features & Use Cases

CI Status Analysis: Analyzes Azure DevOps and Helix CI build and test status for .NET repository pull requests.
Failure Diagnosis: Identifies the root cause of failures, distinguishing between code issues, flaky tests, and infrastructure problems.
Use Case: When a pull request fails its CI checks, use this Skill to get a clear summary of the failures, identify specific failing tests or build errors, and receive actionable recommendations on how to fix them or if it's safe to retry.

Quick Start

Analyze the CI status for pull request number 12345 in the dotnet/runtime repository.

Frequently Asked Questions about ci-analysis

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

FAQPage Schema

How do I debug Azure DevOps CI build failures for .NET pull requests?▼

To debug Azure DevOps CI build failures for .NET pull requests, analyze the build status using the PR number to get detailed diagnostics and actionable recommendations. This distinguishes between code issues, flaky tests, and infrastructure problems.

How can I diagnose flaky tests in Helix CI jobs?▼

Diagnose flaky tests in Helix CI jobs by analyzing the job ID. This identifies whether the failure stems from a code issue or infrastructure problem, providing detailed diagnostics to determine if it is safe to retry the build.

What is the best way to troubleshoot failing .NET PR checks?▼

The best way to troubleshoot failing .NET PR checks is to analyze the CI build and test status using the PR number, build ID, or Helix job ID. This correlates failures with PR changes and searches for known issues.

Can I view build logs to identify root causes of CI test failures?▼

You can view build logs to identify root causes of CI test failures by enabling the log display option during analysis. This provides detailed diagnostics and actionable recommendations to fix build errors or flaky tests.

Does this CI analysis tool support searching for known issues in .NET repositories?▼

This CI analysis tool supports searching for known issues in .NET repositories. It correlates build and test failures with existing known problems and PR changes to deliver detailed diagnostics and actionable fix recommendations.

When should I use a build ID instead of a PR number to analyze CI failures?▼

Use a build ID instead of a PR number to analyze CI failures when you need to target a specific CI build execution directly. Both methods provide detailed diagnostics, but the build ID is useful for isolated build runs.