lbussell/triage-pull-requests
skills/triage-pull-requests/SKILL.md
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.
development
Updated May 12, 2026
$ install --global
skillsauthnpx skillsauth add lbussell/agent-skills triage-pull-requestsInstall 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:53 AM184.2s1 file scanned
SKILL.md
- name:
- triage-pull-requests
- description:
- >-
- 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.
- user-invocable:
- true
- disable-model-invocation:
- true
Workflow
Step 1: List open pull requests
gh pr list
Step 2: Investigate each PR
For each open PR, gather its full context:
- Review & merge status:
gh pr view <number> - CI status: Use the
investigating-pull-requestskill to check pipeline status.
For PRs with CI failures, use the investigating-pipeline skill to read task logs and identify root causes.
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 merged
Step 3: Categorize and present results
Using everything you've learned, place each PR into one of these categories (in this priority order):
- Ready to Merge — Approved, CI passing, no merge conflicts
- Needs Your Review —
lbussellis a requested reviewer - Needs Author Action — Changes requested, CI failing, or merge conflicts
- Stale — No updates in 7+ days and not ready to merge
- Waiting — CI in progress, awaiting reviews from others, recently updated drafts, etc.
Use your judgment when things are ambiguous. For example:
- A PR with only flaky-test failures might still be ready to merge
- A draft PR from the user that hasn't been touched in weeks is stale even if CI is green
For "Needs Author Action" PRs with CI failures, include the root cause diagnosis.
End with a recommended next action.
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-pipelines
development
VerifiedTrustedCommunity
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.
SKILL.mdUpdated May 12, 2026