skills.rest
linuxfoundation
linuxfoundationOFFICIAL
Explore all skills by this author →
WebsiteGitHub

lfx-pr-catchup

Aggregate open pull requests across repositories and classify them by urgency.

8|1|Updated Mar 16, 2026
Search Tags:#github#dashboard#triage#read-only#pull-request#rate-limit#review-signals
One-click install
npx skills add https://github.com/linuxfoundation/lfx-skills --skill lfx-pr-catchup
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: lfx-pr-catchup
Source: https://github.com/linuxfoundation/lfx-skills/tree/main/lfx-pr-catchup
Command: npx skills add https://github.com/linuxfoundation/lfx-skills --skill lfx-pr-catchup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The PR Catch-Up Dashboard provides an at-a-glance view of all open pull requests, surfacing unresolved comments, status changes, stale PRs, and approved-but-not-merged PRs to accelerate triage.

Core Features & Use Cases

  • Compact, terminal-friendly dashboard of open PRs across repositories.
  • Highlights high-priority signals such as unresolved comments and changes requested.
  • Shows stale PRs and approved-but-not-merged PRs to keep teams aligned.
  • Read-only workflow that never modifies code or PRs.

Quick Start

Type /lfx-pr-catchup to generate and render your PR catch-up dashboard.

Frequently Asked Questions about lfx-pr-catchup

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

FAQPage Schema
How do I triage open GitHub pull requests across multiple repositories at a glance?▼

To triage open GitHub pull requests across repositories, you aggregate them into a terminal-friendly dashboard that surfaces unresolved comments, changes requested, and stale PRs. This read-only workflow classifies PRs by urgency to accelerate review triage.

What is the best way to find approved-but-not-merged GitHub PRs that need attention?▼

Finding approved-but-not-merged GitHub PRs is done by aggregating open pull requests and flagging attention-needed signals. The dashboard highlights approved-but-not-merged PRs and unresolved comments to keep teams aligned during triage.

Do I need GitHub CLI to surface review signals for stale pull requests?▼

Yes, surfacing review signals for stale pull requests relies on GitHub CLI and GraphQL-based enrichment steps. These dependencies extract PR status changes and unresolved comments while performing read-only analysis to avoid rate-limit issues.

Can I use a read-only GitHub dashboard to classify stale PRs by urgency without modifying code?▼

You can use a read-only GitHub dashboard to classify stale PRs by urgency without modifying code or PRs. It performs read-only analysis of open pull requests and highlights high-priority signals like unresolved comments and changes requested.

Why does my GitHub pull request triage dashboard return partial data when repositories are inaccessible?▼

GitHub pull request triage dashboards return partial data when repositories are inaccessible due to access restrictions or rate limits. Safeguards are included to handle these edge cases gracefully during GraphQL enrichment without failing the entire read-only analysis.

Related Skills

Explore More Software Engineering Skills→
tobihagemanntobihagemann
399

fetch-pr-comments

Fetch and summarize unresolved GitHub PR review comments via GraphQL.

Community
Intermediate
webrix-aiwebrix-ai
1

pr-automation

Automate GitHub pull request workflows for reviewer assignment, labeling, and merge policy enforcement.

Official
Advanced
luanluan
4

resume-work

Recover development context for a branch or pull request after inactivity.

Community
Intermediate
CalcMarkCalcMark
4

github-project

Manage GitHub issues and project boards with the GitHub CLI.

Official
Advanced