azsdk-common-pipeline-analysis

Diagnose Azure SDK CI/CD pipeline failures into structured root-cause reports.

2.6k|2.2k|Updated Dec 6, 2011
One-click install
npx skills add https://github.com/Azure/azure-sdk-for-java --skill azsdk-common-pipeline-analysis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: azsdk-common-pipeline-analysis
Source: https://github.com/Azure/azure-sdk-for-java/tree/main/.github/skills/azsdk-common-pipeline-analysis
Command: npx skills add https://github.com/Azure/azure-sdk-for-java --skill azsdk-common-pipeline-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Azure SDK CI/CD pipeline failures produce raw logs and test artifacts that are hard to interpret. This Skill turns that raw failure data into a structured diagnosis with root cause, affected files and lines, and concrete fix instructions for each failure.

Core Features & Use Cases

  • Structured Failure Diagnosis: Categorizes each pipeline failure as test, build/compilation, validation/lint, or infrastructure, citing exact file:line locations.
  • Lazy Failure Detail Fetching: Retrieves failed test run or test case data per artifact file to avoid overloading context.
  • Cascading Failure Detection: Groups failures sharing a single root cause instead of listing each individually.
  • Use Case: A developer comments on a PR asking why the CI build broke; the Skill analyzes the pipeline via the azure-sdk-mcp server and returns a markdown report with root cause, per-failure fixes, verify commands, and a fixable-vs-infrastructure summary.

Quick Start

Ask the assistant to analyze your failing Azure SDK pipeline by providing the build ID, pipeline URL, or PR link, for example: analyze why pipeline build 6447834 failed.

Frequently Asked Questions about azsdk-common-pipeline-analysis

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

FAQPage Schema
How do I analyze a failing Azure SDK pipeline build?

Provide the build ID, pipeline URL, or PR link and run the azsdk_analyze_pipeline tool from the azure-sdk-mcp server. It returns failed tasks and a failed test index, which this Skill categorizes and formats into a root-cause diagnosis.

What tool analyzes CI test failures in Azure DevOps pipelines?

The azsdk_analyze_pipeline tool on the azure-sdk-mcp server analyzes pipeline failures using logs and test results. Companion tools like azsdk_get_failed_test_run_data fetch full failure details per artifact file.

Does this Skill fix pipeline failures automatically?

No, it is analysis-only and never edits files. It reports the root cause, affected file:line, and fix instructions, then recommends the azsdk-common-pipeline-fixer skill to apply code fixes.

Can I analyze a pipeline failure from a GitHub PR comment?

Yes, when triggered from a PR comment, provide the PR link and the Skill uses azsdk_get_pr_checks and azsdk_analyze_pipeline to diagnose the failing checks linked to that PR.

Why does pipeline analysis return no failed test data?

This happens when the build ID is wrong, the run has not completed, or test-artifact upload is not configured. In that case the Skill relies on failed task log analysis instead of test artifacts.

When should I retry a pipeline instead of fixing code?

Retry when failures are infrastructure-related, such as DNS errors, HTTP 429 throttling, agent disconnects, package download timeouts, or SSL errors. The Skill marks these as infrastructure failures rather than code-fixable issues.