lbussell/triage-pipelines
skills/triage-pipelines/SKILL.md
List all failing and warning Azure Pipelines for daily triage. Checks preconfigured pipeline folders and reports any with failed or warning builds. Use for daily pipeline health checks.
development
Updated May 12, 2026
$ install --global
skillsauthnpx skillsauth add lbussell/agent-skills triage-pipelinesInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 12, 2026, 6:52 AM108.2s2 files scanned
SKILL.md
- name:
- triage-pipelines
- description:
- >-
Workflow
Step 1: List failing pipelines
# Get failing pipelines for the current repo.
dotnet scripts/GetFailingPipelines.cs
# (Optionally) override auto-detected values
dotnet scripts/GetFailingPipelines.cs --org myorg --azdo-project myproject --folder owner/repo
Step 2: Investigate each failure
For each failing pipeline in the output, use the investigating-pipeline skill with the build ID to see the timeline and read task logs.
Step 3: Correlate failures with recent pull requests and issues
- Check recent issues:
gh issue list --state all - Check recent pull requests:
gh pr list --state all
Look for the following things:
- Is there a recent change that obviously caused this failure?
- Is this failure a known issue?
- Is there already a pull request open that addresses the failure?
Related Skills
lbussell/triaging-issues
development
VerifiedTrustedCommunity
Triage issues labeled 'untriaged' in a repository. Investigates each issue, correlates with recent activity, and categorizes into: customer issue, ready for work, needs investigation, or already addressed. Informational only — does not modify issues.
SKILL.mdUpdated May 21, 2026
lbussell/creating-pull-requests
tools
VerifiedTrustedCommunity
Open a pull request on GitHub. Use when the user asks to open or create a pull request on GitHub.
SKILL.mdUpdated May 14, 2026
lbussell/creating-issues
devops
VerifiedTrustedCommunity
Open an issue on GitHub. Use when the user asks to file/open/draft/create an issue. Useful for bug reports, pipeline failures, feature requests, etc.
SKILL.mdUpdated May 14, 2026
lbussell/triage-pull-requests
development
VerifiedTrustedCommunity
Triage open pull requests in a repository into actionable categories: ready to merge, needs review, needs action, stale, waiting. Use for daily PR triage to quickly identify what needs attention.
SKILL.mdUpdated May 12, 2026