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
Broaden skill to CI status analysis, add job summary
- Update SKILL.md description to cover CI status checks, not just failures
- Add trigger phrases: 'is CI passing', 'build status', 'ready to merge'
- Add job summary in build output (e.g., '143 total: 142 passed, 1 failed')
- Improve no-build-found message to explain CI hasn't been triggered
Copy file name to clipboardExpand all lines: .github/skills/azdo-helix-failures/SKILL.md
+6-4Lines changed: 6 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,19 +1,21 @@
1
1
---
2
2
name: azdo-helix-failures
3
-
description: Retrieve and analyze test failures from Azure DevOps builds and Helix test runs for dotnet repositories. Use when investigating CI failures, debugging failing PRs, or given URLs containing dev.azure.com or helix.dot.net.
3
+
description: Analyze 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.
4
4
---
5
5
6
-
# Azure DevOps and Helix Failure Analysis
6
+
# Azure DevOps and Helix CI Analysis
7
7
8
-
Analyze CI test failures in Azure DevOps and Helix for dotnet repositories (runtime, sdk, aspnetcore, roslyn, and more).
8
+
Analyze CI build status and test failures in Azure DevOps and Helix for dotnet repositories (runtime, sdk, aspnetcore, roslyn, and more).
9
9
10
10
## When to Use This Skill
11
11
12
12
Use this skill when:
13
+
- Checking CI status on a PR ("is CI passing?", "what's the build status?")
13
14
- Investigating CI failures or checking why a PR's tests are failing
15
+
- Determining if a PR is ready to merge based on CI results
14
16
- Debugging Helix test issues or analyzing build errors
15
17
- Given URLs containing `dev.azure.com`, `helix.dot.net`, or GitHub PR links with failing checks
16
-
- Asked questions like "why is this PR failing", "analyze the CI failures", or "what's wrong with this build"
18
+
- Asked questions like "why is this PR failing", "analyze the CI", "is CI green", or "what's the build status"
0 commit comments