Agent skill

triage-pull-requests

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.

View SKILL.md on GitHub Repository
Stars 0
Forks 0

Install this agent skill to your Project

npx add-skill https://github.com/lbussell/agent-skills/tree/main/skills/triage-pull-requests

SKILL.md

Workflow

Step 1: List open pull requests

shell
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-request skill 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):

  1. Ready to Merge — Approved, CI passing, no merge conflicts
  2. Needs Your Review — lbussell is a requested reviewer
  3. Needs Author Action — Changes requested, CI failing, or merge conflicts
  4. Stale — No updates in 7+ days and not ready to merge
  5. 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.

Recommended Agent Skills

Expand your agent's capabilities with these related and highly-rated skills.

lbussell/agent-skills

create-sub-agent-worktree

Spawn a Copilot CLI agent in its own git worktree and tmux window. Creates a new branch via worktrunk (`wt`), opens a tmux window in the target session, and launches `copilot -i` with a prompt. Use when the user asks to run a task in parallel, hand off work to another agent, or start a background coding task in a separate worktree.

0 0
Explore
lbussell/agent-skills

triage-followup

Produce a follow-up document from a .NET containers triage meeting. Takes a VTT transcript and correlates it with the user's recent GitHub activity to produce a markdown document with concrete to-dos and links. Use after a triage meeting when the user has a .vtt transcript file.

0 0
Explore
lbussell/agent-skills

property-testing-cscheck

Write property-based tests in C# using CsCheck. Covers generator composition, property selection (round-trip, invariant, model-based, metamorphic), parallel linearizability testing, performance comparison, classification, and configuration. Use when writing, reviewing, or improving property-based tests in a .NET project that uses CsCheck.

0 0
Explore
lbussell/agent-skills

investigating-pull-request

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.

0 0
Explore
lbussell/agent-skills

triage-pipelines

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.

0 0
Explore
lbussell/agent-skills

investigating-pipeline

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.

0 0
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results