skills.rest
lewing
lewingCOMMUNITY
Explore all skills by this author →
𝕏@lewingGitHub

ci-analysis

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

4|1|Updated Feb 19, 2026
Search Tags:#timeline#log-analysis#azure-devops#build-analysis#pr-checks#helix#ci-analysis
One-click install
npx skills add https://github.com/lewing/agent-plugins --skill ci-analysis-lewing
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ci-analysis
Source: https://github.com/lewing/agent-plugins/tree/main/plugins/dotnet-dnceng/skills/ci-analysis
Command: npx skills add https://github.com/lewing/agent-plugins --skill ci-analysis-lewing

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Analyses CI build and test status from Azure DevOps and Helix for dotnet repository PRs. Use when checking CI status, investigating failures, determining if a PR is ready to merge, or given URLs containing dev.azure.com or helix.dot.net. Also use when asked "why is CI red", "test failures", "retry CI", "rerun tests", "is CI green", "build failed", or "checks failing". DO NOT USE FOR: investigating stale codeflow PRs or dependency update health, tracing whether a commit has flowed from one repo to another, reviewing code changes for correctness or style.

Core Features & Use Cases

  • Collects and analyzes CI status from Azure DevOps and Helix for dotnet PRs
  • Correlates failures with PR changes, historical runs, and known issues
  • Provides actionable recommendations and links to Build Analysis and Helix artifacts

Quick Start

Analyze the CI status for a given PR or build and report failures, known issues, and recommended next steps.

Frequently Asked Questions about ci-analysis

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

FAQPage Schema
How do I analyze Azure DevOps build failures for dotnet PRs?▼

To analyze Azure DevOps build failures, the Skill collects CI status for dotnet PRs, identifies failing builds, gathers logs, and maps failures to known issues and correlated PR changes to provide actionable recommendations.

Why is CI red on my Azure DevOps pull request?▼

CI may be red due to failing builds or test failures. This Skill investigates failure details from Azure DevOps and Helix, correlating them with historical runs and known issues to explain why checks are failing.

Can I use this to check if my dotnet PR is ready to merge?▼

Yes, you can check if a PR is ready to merge. The Skill analyzes current CI status across Azure DevOps and Helix, reporting any failing builds or test failures that would block the merge.

Does the CI analysis require the GitHub CLI to investigate build logs?▼

Yes, the GitHub CLI (gh) is required. The Skill depends on the gh tool to gather PR information and CI logs from Azure DevOps and Helix to perform build analysis and map failures to known issues.

When should I not use this Skill for investigating CI failures?▼

Do not use this Skill for investigating stale codeflow PRs, dependency update health, tracing commits between repos, or reviewing code changes for correctness and style; it is strictly for CI status and build failure analysis.

Related Skills

Explore More Software Engineering Skills→
poisontr33spoisontr33s

gh-address-comments

Redirect PR comment workflows to gh-fix-ci for fetch, triage, and apply-fixes.

Community
Basic
ilonatommyilonatommy
3

ci-analysis

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

Community
Advanced
OpenLaborOpenLabor
4

Code Review

Automate targeted code review of GitHub pull requests for defects and quality issues.

Official
Intermediate
dotnetdotnet
18.2k

vmr-codeflow-status

Analyze VMR codeflow PR status across dotnet repositories for freshness and flow health.

Official
Advanced