skills.rest
CoolCoderSuper
CoolCoderSuperCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

ci-analysis

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

4|1|Updated May 1, 2026
Search Tags:#logs#triage#ci#azure-devops#powershell#build-status#helix
One-click install
npx skills add https://github.com/CoolCoderSuper/vb-ls --skill ci-analysis-coolcodersuper
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ci-analysis
Source: https://github.com/CoolCoderSuper/vb-ls/tree/main/roslyn/.github/skills/ci-analysis
Command: npx skills add https://github.com/CoolCoderSuper/vb-ls --skill ci-analysis-coolcodersuper

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps developers triage and analyze CI failures for dotnet repositories by aggregating PR CI status from Azure DevOps and Helix, surfacing failures, logs, and known issues to guide remediation.

Core Features & Use Cases

  • Gather PR CI context, identify failed Azure DevOps jobs and Helix work items, and fetch console logs for detailed failure analysis.
  • Correlate failures with PR changes, surface Known Build Issues via Build Analysis, and produce a structured [CI_ANALYSIS_SUMMARY] output to inform remediation.
  • Support multiple input modes: PRNumber, BuildId, or HelixJob/WorkItem, enabling flexible investigations across the CI pipeline.

Quick Start

Run Get-CIStatus.ps1 with a PR number or a BuildId to fetch failing CI details and emit a structured summary.

Frequently Asked Questions about ci-analysis

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

FAQPage Schema
How do I triage CI failures in Azure DevOps for a dotnet runtime PR?▼

You can triage CI failures by running a PowerShell script with the PR number to fetch failing Azure DevOps jobs and Helix work items, retrieve console logs, and surface known build issues for remediation.

Can I analyze Helix work items and Azure DevOps build logs without a PR number?▼

Yes, you can analyze Helix work items and Azure DevOps build logs without a PR number by passing a BuildId or HelixJob and WorkItem parameters to investigate failures across the CI pipeline.

Does the CI failure analysis tool support dotnet sdk and roslyn repositories?▼

Yes, the CI failure analysis supports dotnet sdk and roslyn repositories, aggregating PR CI status from Azure DevOps and Helix to surface failures, logs, and known build issues.

What is the best way to identify known build issues when diagnosing Helix CI failures?▼

The best way to identify known build issues when diagnosing Helix CI failures is to use Build Analysis to correlate failures with PR changes and produce a structured CI summary to inform remediation and retries.

Do I need the gh CLI to run Azure DevOps CI analysis scripts?▼

Yes, you need the gh CLI dependency to run the Azure DevOps CI analysis scripts that gather PR context, identify failed jobs, and fetch console logs for detailed failure analysis.

How do I get a structured summary of Azure Devops and Helix CI failures for retries?▼

You get a structured summary of Azure DevOps and Helix CI failures by running the analysis script, which outputs a structured JSON summary alongside human-readable output to guide remediation and retries.

Related Skills

Explore More Software Engineering Skills→
lewinglewing
4

ci-analysis

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

Community
Advanced
whichguywhichguy

webhook-subscriptions

Subscribe to webhook events and trigger automated Hermes agent runs.

Community
Intermediate
ilonatommyilonatommy
3

ci-analysis

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

Community
Advanced
dotnetdotnet
13

ci-crash-dump

Identify crashed Helix work items and retrieve crash artifacts from dotnet CI runs.

Official
Advanced