You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .github/skills/azsdk-common-pipeline-analysis/SKILL.md
+16-12Lines changed: 16 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ license: MIT
4
4
metadata:
5
5
version: "1.0.0"
6
6
distribution: shared
7
-
description: 'Analyze Azure SDK CI/CD pipeline failures into a structured diagnosis, and define the required output format. Load this skill before calling azsdk_analyze_pipeline, which returns raw failure data that this skill interprets and formats. USE FOR: "pipeline failed", "build failure", "CI check failing", "tests failing in CI", "analyze pipeline", "debug SDK pipeline". DO NOT USE FOR: local build issues without pipeline context, API design review, SDK publishing, applying code fixes (instead use azsdk-common-pipeline-fixer). INVOKES: azure-sdk-mcp:azsdk_analyze_pipeline, azure-sdk-mcp:azsdk_get_pipeline_llm_artifacts, azure-sdk-mcp:azsdk_get_pr_checks, azure-sdk-mcp:azsdk_get_pipeline_status.'
7
+
description: 'Analyze Azure SDK CI/CD pipeline failures into a structured diagnosis, and define the required output format. Load this skill before calling azsdk_analyze_pipeline, which returns raw failure data that this skill interprets and formats. USE FOR: "pipeline failed", "build failure", "CI check failing", "tests failing in CI", "analyze pipeline", "debug SDK pipeline". DO NOT USE FOR: local build issues without pipeline context, API design review, SDK publishing, applying code fixes (instead use azsdk-common-pipeline-fixer). INVOKES: azure-sdk-mcp:azsdk_analyze_pipeline, azure-sdk-mcp:azsdk_get_pipeline_llm_artifacts, azure-sdk-mcp:azsdk_get_failed_test_run_data, azure-sdk-mcp:azsdk_get_failed_test_case_data, azure-sdk-mcp:azsdk_get_pr_checks, azure-sdk-mcp:azsdk_get_pipeline_status.'
8
8
compatibility: "azure-sdk-mcp server, Azure DevOps pipeline build ID or GitHub PR link"
9
9
---
10
10
@@ -22,20 +22,24 @@ This skill analyzes Azure SDK CI/CD pipeline failures and provides a structured
|`azure-sdk-mcp:azsdk_analyze_pipeline`| Analyze pipeline failure (logs + test results) |
28
+
|`azure-sdk-mcp:azsdk_get_pipeline_llm_artifacts`| Download test result artifacts from pipeline |
29
+
|`azure-sdk-mcp:azsdk_get_failed_test_run_data`| Full details for every failure in one artifact file |
30
+
|`azure-sdk-mcp:azsdk_get_failed_test_case_data`| Full details for a single failing test in a file |
31
+
|`azure-sdk-mcp:azsdk_get_pr_checks`| Get pipeline/check results linked to a PR |
32
+
|`azure-sdk-mcp:azsdk_get_pipeline_status`| Get pipeline run status |
31
33
32
34
## Steps
33
35
34
36
1.**Identify** - Get the build ID, pipeline URL, or PR link (use the PR link when triggered from a PR comment).
35
-
2.**Analyze** - Run `azsdk_analyze_pipeline`. It returns `failed_tasks` (log errors from failed steps) and `failed_test_titles` (failed tests grouped by file).
36
-
3.**Categorize** each failure: test, build/compilation, validation/lint, or infrastructure.
37
-
4.**Diagnose** - Give each failure's root cause and affected file(s)/line(s), and note if several share one root cause. See [failure patterns](references/failure-patterns.md).
38
-
5.**Report** - Use the [output format](references/output-format.md): root cause, affected files, per-failure fix + verify command, and fixable vs infrastructure. Recommend `azsdk-common-pipeline-fixer` to apply fixes.
37
+
2.**Analyze** - Run `azsdk_analyze_pipeline`. It returns `failed_pipeline_tasks` (log errors from failed steps) and `failed_pipeline_tests`, a lightweight index of failed tests grouped by artifact file. Each entry has `artifact_file_path`, `platform`, and `failed_test_titles` — titles only, no error text, to keep the response small.
38
+
3.**Fetch failure details** - Fetch failure details lazily so you don't overload context: call `azsdk_get_failed_test_run_data` with the parameter `failedTestRunsPath` set to `artifact_file_path` once per file to get every failure in it. Or call `azsdk_get_failed_test_case_data` with
39
+
`failedTestRunsPath` set to `artifact_file_path` and `testCaseTitle` set to one exact title from `failed_test_titles`. Prefer the per-file call when triaging a whole file's failures.
40
+
4.**Categorize** each failure: test, build/compilation, validation/lint, or infrastructure.
41
+
5.**Diagnose** - Give each failure's root cause and affected file(s)/line(s), and note if several share one root cause. See [failure patterns](references/failure-patterns.md).
42
+
6.**Report** - Use the [output format](references/output-format.md): root cause, affected files, per-failure fix + verify command, and fixable vs infrastructure. Recommend `azsdk-common-pipeline-fixer` to apply fixes.
39
43
40
44
## Examples
41
45
@@ -46,5 +50,5 @@ This skill analyzes Azure SDK CI/CD pipeline failures and provides a structured
46
50
## Troubleshooting
47
51
48
52
- If `azsdk_analyze_pipeline` returns no data, verify the build ID is correct and the run has completed.
49
-
- If `failed_test_titles` is empty, rely on `failed_tasks` log analysis (test-artifact upload may not be configured).
53
+
- If `failed_pipeline_tests` is empty, rely on `failed_pipeline_tasks` log analysis (test-artifact upload may not be configured).
50
54
- For a private/internal pipeline, the user may need to `az login`. See [failure patterns](references/failure-patterns.md).
0 commit comments