fetching-github-prs-to-review

Fetch GitHub pull requests awaiting review and format them as markdown.

24|3|Updated Aug 2, 2020
One-click install
npx skills add https://github.com/ooloth/dotfiles --skill fetching-github-prs-to-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fetching-github-prs-to-review
Source: https://github.com/ooloth/dotfiles/tree/main/tools/claude/config/skills/fetching-github-prs-to-review
Command: npx skills add https://github.com/ooloth/dotfiles --skill fetching-github-prs-to-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fetches GitHub pull requests waiting for review and presents a fully formatted markdown display, categorized by type and with status metadata to speed decision making.

Core Features & Use Cases

  • Grouping: PRs are categorized into Feature/Bug, Chores, Dependency Updates.
  • Status details: CI status, review status, conflicts, and activity are summarized.
  • Output: Returns ready-to-display markdown for review sessions.

Quick Start

Run the script to fetch and format your PRs waiting for review: python3 ~/.claude/skills/fetching-github-prs-to-review/fetch_prs.py

Frequently Asked Questions about fetching-github-prs-to-review

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

FAQPage Schema
How do I organize GitHub pull requests waiting for review?

Fetch and organize GitHub pull requests awaiting review by grouping them into Feature/Bug, Chores, and Dependency Updates categories, sorted by age with CI status, review activity, and size metrics displayed in formatted markdown to streamline triage decisions.

Can I automate fetching my GitHub PR review queue?

Yes, automate PR fetching using GraphQL to query repositories where you're requested as a reviewer, automatically categorizing and formatting results with CI status, review status, and viewing history to reduce manual backlog management.

What information does a GitHub PR review summary typically include?

A comprehensive PR summary includes CI status, review status, merge conflicts, activity history, human-readable age, time-to-review estimates, and size metrics—all formatted in markdown for quick decision-making during review sessions.

How do I reduce GitHub PR review backlog efficiently?

Reduce backlog by fetching all pending PRs, categorizing by type and age, and displaying cached markdown output with status metadata and metrics to prioritize reviews and identify stale requests quickly.

Does GitHub PR review automation work across multiple repositories?

Yes, the automation fetches PRs from all repositories where you're listed as a requested reviewer, applies consistent categorization and formatting, and caches results for efficient subsequent access across your workflow.

What metadata helps prioritize GitHub pull requests for review?

Prioritize using CI status, review status, PR age, time estimates, size metrics, and viewing history—metadata computed and grouped by type to highlight urgent or aging PRs and conflicts requiring immediate attention.