My Pull Requests

my-pull-requests skill for programming & development

A personal pull request management skill that provides a unified view of your authored and review-requested PRs across all repositories, with filtering, status tracking, and quick actions.

What Is This?

Overview

This skill consolidates all pull requests you have authored or been requested to review across multiple repositories. It provides status summaries including CI checks, review approvals, merge conflicts, and staleness indicators for efficient PR management from the terminal.

Who Should Use This

Perfect for developers managing PRs across multiple repos, code reviewers tracking their review queue, team leads monitoring team PR velocity, and contributors needing a consolidated PR dashboard.

Why Use It?

Problems It Solves

Active developers often have PRs open in several repositories simultaneously. Tracking review status, CI results, and merge readiness across repos requires constant browser tab switching. This skill provides instant visibility into all your PR activity from one place.

Core Highlights

Authored PRs - See all your open PRs with CI and review status
Review Queue - List PRs awaiting your review across all repos
Status Summary - CI pass/fail, approval count, and conflict indicators
Quick Actions - Merge, approve, or request changes from terminal
Staleness Detection - Identify PRs with no recent activity

How to Use It?

Basic Usage

Ask Claude about your pull requests, and this skill queries GitHub for your PR activity.

Scenario 1: Viewing Your PR Dashboard

Ask Claude: "Show all my open pull requests"

Claude will query:

gh search prs --author=@me --state=open --json repository,title,reviewDecision,statusCheckRollup --jq '.[] | "\(.repository.name): \(.title) [\(.reviewDecision)]"'

gh search prs --review-requested=@me --state=open

gh pr view 123 --repo owner/project --json state,reviews,statusCheckRollup

gh search prs --author=@me --merged=">$(date -d '7 days ago' +%Y-%m-%d)"

Scenario 2: Quick PR Actions

Tell Claude: "Merge my approved PR in the api-service repo"

Claude will execute:

gh pr merge 45 --repo owner/api-service --squash --delete-branch

gh pr review 78 --repo owner/frontend --approve --body "LGTM, clean implementation"

gh pr review 92 --repo owner/backend --request-changes --body "Please add error handling for the edge case on line 42"

Real-World Examples

Weekly PR Cleanup

A senior developer ran weekly PR audits, identifying 3 stale PRs with unresolved conflicts and 5 awaiting review for over a week. Batch reminders to reviewers cleared the backlog within 2 days.

Code Review Efficiency

A team lead tracked their review queue across 8 repositories. Sorting by age ensured oldest PRs got reviewed first, reducing average review turnaround from 3 days to under 24 hours.

Advanced Tips

PR Metrics Tracking

Script weekly PR counts (opened, merged, time-to-merge) to track your development velocity over time. Export data to CSV for trend analysis.

Review Reminder Automation

Combine PR search with notification scripts to send Slack reminders for PRs awaiting review for more than 48 hours.

When to Use It?

Use Cases

Morning Review - Check PR status and review queue at start of day
Merge Readiness - Identify PRs ready to merge across repositories
Review Tracking - Monitor your pending review obligations
Sprint Metrics - Count PRs merged during a sprint period
Stale PR Cleanup - Find and close abandoned pull requests

Important Notes

Requirements

GitHub CLI (gh) version 2.0+ installed and authenticated
Repository access for viewing PR details and status checks
Write access for merge, approve, and review actions
Organization membership for org-wide PR searches

Usage Recommendations

Do:

Review daily - Check your review queue at least once per day
Respond to feedback - Address review comments promptly to keep PRs moving
Clean up stale PRs - Close or update PRs that have been idle too long
Use squash merges - Keep commit history clean with squash and merge

Don't:

Don't let PRs age - Merge conflicts grow worse over time
Don't skip CI checks - Always wait for passing status checks before merging
Don't ignore review requests - Blocked reviewers slow the entire team

Limitations

Cross-organization PR searches require separate authentication
GitHub API rate limits apply to bulk queries
Draft PRs may not appear in all search results by default
Review status aggregation may not reflect partial approvals

More Skills You Might Like

Explore similar skills to enhance your workflow