skills/investigating-pull-request/SKILL.md
Shows the CI status for a single GitHub pull request. Displays PR metadata (title, author, fork, branch) and renders Azure Pipelines build timeline trees for each pipeline run. Use when a user provides a PR number or URL and wants to check its CI status or diagnose failures.
npx skillsauth add lbussell/agent-skills investigating-pull-requestInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
# By PR number (auto-detects repo from 'gh repo set-default --view')
dotnet scripts/GetPullRequestStatus.cs 123
# By PR number with explicit repo
dotnet scripts/GetPullRequestStatus.cs 123 --repo owner/repo
# Show all tasks, not just failing ones
dotnet scripts/GetPullRequestStatus.cs 123 --show-all
The script auto-detects the GitHub repository via gh repo set-default --view when --repo is not provided. It outputs PR metadata followed by a build timeline tree for each Azure Pipelines run. Non-Azure checks (GitHub Actions, etc.) are listed separately at the end.
To dig deeper into a specific failing build, use the investigating-pipeline skill with the build ID shown in the output.
development
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.
tools
Open a pull request on GitHub. Use when the user asks to open or create a pull request on GitHub.
devops
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.
development
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.