pr-status

Visualize GitHub pull request stacks and identify stale local branches.

1|Updated Jul 22, 2026

Search Tags:#automation #git #workflow #github #cleanup #pull-request

Ready to run

npx skills add https://github.com/wyattjoh/skills --skill pr-status-wyattjoh

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pr-status
Source: https://github.com/wyattjoh/skills/tree/main/skills/pr-status
Command: npx skills add https://github.com/wyattjoh/skills --skill pr-status-wyattjoh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the challenge of managing multiple concurrent pull requests by providing a clear, consolidated view of your active work and identifying local branches that are safe to delete after a merge.

Core Features & Use Cases

Stack Visualization: Automatically groups open pull requests by their stack metadata, allowing you to see the hierarchy of your changes.
Cleanup Automation: Identifies local branches that have already been merged remotely, helping you keep your local environment clean and organized.
Contextual Reporting: Provides a summary of PR status, including draft states and CI check results, directly in your terminal.

Quick Start

Ask the agent to show your current PR status or run the pr-status command to see a graph of your open pull requests and cleanup candidates.

Frequently Asked Questions about pr-status

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

FAQPage Schema

How do I visualize stacked pull requests in git?▼

You can visualize stacked pull requests by aggregating GitHub PR metadata and branch hierarchy data within your local git repository. This Skill maps branch relationships and sync states to group open pull requests by their stack configurations, displaying the hierarchy of your changes.

How do I find and cleanup stale local git branches after merging?▼

To cleanup stale local git branches, this Skill identifies local branches that have already been merged remotely. By checking merge status for the authenticated user, it highlights cleanup candidates to help keep your local environment organized.

Do I need the GitHub CLI to check pull request status and stack configurations?▼

Yes, you need the GitHub CLI (gh) and local git configuration to check pull request status. The Skill operates within git repositories and requires gh to map branch relationships, aggregate PR metadata, and sync states for the authenticated user.

What is the best way to manage multiple concurrent GitHub pull requests?▼

The best way to manage multiple concurrent GitHub pull requests is to consolidate your active work into a single view. This Skill provides stack visualization, cleanup automation for merged branches, and contextual reporting including draft states and CI check results.

Can I see CI check results and draft states for open pull requests in my terminal?▼

Yes, you can see CI check results and draft states directly in your terminal. The Skill provides contextual reporting that summarizes PR status for your open pull requests, allowing you to review CI checks and draft states without leaving your local environment.

Why are my local git branches not syncing with merged remote pull requests?▼

Local git branches may not sync with merged remote pull requests if the local branch relationships and merge status are not properly mapped. This Skill aggregates PR metadata to identify stale local branches that are safe to delete after a remote merge.