lbussell/investigating-pipeline
skills/investigating-pipeline/SKILL.md
Diagnoses a single Azure Pipelines build. Shows the build timeline tree with stages, jobs, and task results, and retrieves task logs for debugging failures. Use when a user provides a build ID or Azure DevOps build URL and wants to understand what failed and why.
development
Updated May 12, 2026
$ install --global
skillsauthnpx skillsauth add lbussell/agent-skills investigating-pipelineInstall 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 AM158.5s3 files scanned
SKILL.md
- name:
- investigating-pipeline
- description:
- >-
Workflow
Step 1: View the build timeline
dotnet scripts/GetBuildTimeline.cs <buildId> --org <org> --azdo-project <project>
This prints a tree of stages, jobs, and tasks. By default only failing and warning tasks are shown. Use --show-all to see everything.
Each node includes a log ID (e.g., Task #42). Note the log IDs of failing tasks for the next step.
Step 2: Read a failing task's log
dotnet scripts/GetTaskLog.cs <buildId> <logId> --org <org> --azdo-project <project>
This prints the full log for a specific task. Use this to understand the root cause of a 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