github-scan-prs

Scans GitHub repositories for pull requests needing attention and produces a tiered triage report.

2|Updated Apr 4, 2026

Search Tags:#code review #github #prioritization #pull requests #gh cli #triage #scan

Ready to run

npx skills add https://github.com/DoctorMozg/claude-pipelines --skill github-scan-prs-doctormozg

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: github-scan-prs
Source: https://github.com/DoctorMozg/claude-pipelines/tree/main/plugins/mz-dev-git/skills/github-scan-prs
Command: npx skills add https://github.com/DoctorMozg/claude-pipelines --skill github-scan-prs-doctormozg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Engineers juggling multiple GitHub repositories lose track of which pull requests need their review, response, or action. This Skill scans all specified repos and produces a single prioritized triage report so nothing slips through. ## Core Features & Use Cases - Multi-repo PR scanning: Dispatches a scanner agent to find PRs where you are requested for review, mentioned, assigned, or have changes requested on your own PRs. - Tiered prioritization: Scores every PR into Tier 1 (directly asked, unanswered), Tier 2 (review or action requested), or Tier 3 (informational), ranked by complexity and age. - Use Case: Each morning, run the scan across your team's repositories to get a daily PR inbox report, then deep-review any single PR with the separate review command. ## Quick Start Ask the assistant to scan PRs across owner/repo1 and owner/repo2 and show which pull requests need your attention today.

Frequently Asked Questions about github-scan-prs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I check which GitHub PRs need my review across multiple repos?▼

Provide a list of repositories as owner/repo pairs, comma-separated values, or URLs, and the scan finds PRs where you are requested for review, mentioned, or assigned. Results are ranked into three priority tiers in a triage report.

How are pull requests prioritized in the triage report?▼

Every PR is scored into Tier 1 (directly asked, unanswered), Tier 2 (review or action requested), or Tier 3 (informational). Tier boundaries are absolute, and PRs are ranked within each tier by complexity and age.

Can I scan PRs without specifying a repository list?▼

Yes, if no arguments are given, the current repository is detected via gh repo view. If detection fails through the CLI, MCP tools, and REST API fallbacks, you are asked to provide the repository explicitly.

Does this skill perform deep code reviews of pull requests?▼

No, it only produces a triage report identifying which PRs need attention. For a thorough review of a single PR, run the separate github-review-pr command on that PR's URL.

What happens when the PR scan returns zero results?▼

The scanner emits verification tokens distinguishing a confirmed empty inbox from an unverified failure. Unverified zero results surface a warning prompting you to check the GitHub username and repo list rather than silently reporting all clear.