list-prs

Lists open GitHub pull requests across repositories with status, dependencies, and review priority.

Updated Dec 25, 2021
One-click install
npx skills add https://github.com/kotahashihama/dotfiles --skill list-prs-kotahashihama
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: list-prs
Source: https://github.com/kotahashihama/dotfiles/tree/main/home/.claude/skills/list-prs
Command: npx skills add https://github.com/kotahashihama/dotfiles --skill list-prs-kotahashihama

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When your work spans frontend, backend, and infrastructure repositories, tracking your own open pull requests becomes fragmented. This Skill aggregates all your open PRs into a single table showing what each PR does, what it depends on, whether it is blocked, and how urgently it needs review. ## Core Features & Use Cases - Cross-Repository PR Aggregation: Collects open PRs authored by you across all locally cloned repositories using the GitHub CLI, in parallel. - Dependency and Staleness Detection: Extracts PR references from descriptions and comments, checks the state of referenced PRs, and flags stale references such as merged prerequisites or closed links. - Action and Priority Classification: Categorizes each PR as mergeable, awaiting review, blocked on you, or blocked externally, and assigns review urgency (high/medium/low) based on user-facing impact. - Use Case: You ask "what PRs do I have open right now?" and receive one consolidated table plus a copy-paste-ready review request URL list ordered by priority and dependency. ## Quick Start Ask the assistant to list all PRs you are currently responsible for across your repositories and summarize their status and next actions.

Frequently Asked Questions about list-prs

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

FAQPage Schema
How do I list all my open GitHub PRs across multiple repositories?

Run gh pr list --author @me --state open in each locally cloned repository, issuing the calls in parallel. This Skill automates that by enumerating repositories under your GitHub org directory and merging results into one table.

How to check if a GitHub PR has been approved using the gh CLI?

Query the GraphQL field latestOpinionatedReviews and check for any node with state APPROVED. The reviewDecision field can return null even when approved depending on repository rulesets, and latestReviews can miss approvals.

Can this Skill detect dependencies between PRs in different repositories?

Yes. It parses PR bodies and comments for references like owner/repo#123, then fetches each referenced PR's state with gh pr view. It reports which side is blocking and flags stale references to merged or closed PRs.

Does this Skill merge, close, or mark PRs as ready?

No. It is read-only: it lists and classifies PRs but never changes their state. When it finds a stale PR description, it only suggests running a separate update skill rather than editing anything itself.

Why does a draft PR not always mean the PR is blocked?

A draft may simply be ready but unsubmitted. The Skill checks CI status and dependency contracts to judge whether review feedback would still be valid, and reports whether the draft can safely be marked ready.