list-prs

Aggregate open pull request statuses from multiple GitHub repositories.

3|1|Updated Oct 9, 2025
One-click install
npx skills add https://github.com/OmniNode-ai/omniclaude --skill list-prs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: list-prs
Source: https://github.com/OmniNode-ai/omniclaude/tree/main/plugins/onex/skills/list-prs
Command: npx skills add https://github.com/OmniNode-ai/omniclaude --skill list-prs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a consolidated view of all open pull requests across multiple repositories, helping teams stay informed about code review status and mergeability.

Core Features & Use Cases

  • Centralized Dashboard: View open PRs from various OmniNode-ai repositories in one place.
  • Status at a Glance: See CI status, mergeability, and review decisions for each PR.
  • Filtering Options: Focus on specific repositories or view only merge-ready PRs.
  • Use Case: A team lead can quickly assess the overall health of ongoing development by running this skill to identify PRs that are blocked or ready for immediate merging.

Quick Start

Run the list-prs skill to see all open pull requests across the default repositories.

Frequently Asked Questions about list-prs

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

FAQPage Schema
How do I view open pull requests across multiple GitHub repositories in one place?

You can view open pull requests across multiple GitHub repositories by using a dashboard aggregator that fetches PR statuses via the GitHub CLI. It displays CI status, mergeability, and review decisions for each repository in a single consolidated view.

How can I check the CI status and mergeability of GitHub pull requests?

To check the CI status and mergeability of GitHub pull requests, run an aggregation skill that retrieves this data via the GitHub CLI. It displays continuous integration results and merge readiness for each open PR.

Do I need the GitHub CLI to monitor open pull request statuses?

Yes, you need the GitHub CLI installed to monitor open pull request statuses, as the aggregation skill relies on it for data retrieval. The CLI queries your repositories to fetch CI status, mergeability, and review decisions.

What's the best way to find merge-ready pull requests across my codebase?

The best way to find merge-ready pull requests is to use a PR monitoring skill with filtering options. It aggregates open PRs across repositories and allows you to filter for those that are fully reviewed and ready for immediate merging.

Can I filter pull requests by specific repositories or merge readiness?

Yes, you can filter pull requests by specific repositories or merge readiness. The PR monitoring skill provides filtering options to focus on particular repos or to view only the pull requests that are currently merge-ready.

Why should I use a pull request dashboard instead of checking repos individually?

A pull request dashboard saves time by providing a clear overview of development progress and potential blockers across all repos at once. It eliminates the need to manually check each repository for CI status and review decisions individually.