pr-status

Assess mergeability and review/CI status of GitHub pull requests.

2|Updated Jun 2, 2024
One-click install
npx skills add https://github.com/magnusrodseth/dotfiles --skill pr-status-magnusrodseth
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-status
Source: https://github.com/magnusrodseth/dotfiles/tree/main/.claude/skills/pr-status
Command: npx skills add https://github.com/magnusrodseth/dotfiles --skill pr-status-magnusrodseth

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, jq, and includes scripts (resource) components.

What problem does it solve?

The pr-status skill provides a comprehensive overview of the status, mergeability, and review/CI status of GitHub pull requests in a compact, easily readable format, saving users time by eliminating the need to navigate to each pull request.

Core Features & Use Cases

  • Mergeability: Determines whether a pull request can be merged or not.
  • Review/CI Status: Displays the latest status of review comments and continuous integration checks.
  • Use Case: Ideal for project managers and developers to quickly get a summary of their PRs or PRs owned by someone else to ensure everything is on track for merging.

Quick Start

Run 'bash scripts/pr-status.sh your-pr-reference' to get a status summary for a specific PR.

Frequently Asked Questions about pr-status

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

FAQPage Schema
How do I check the mergeability and CI status of a GitHub pull request from the command line?

Check GitHub pull request mergeability and CI status directly from the command line by running a script that retrieves real-time data via the GitHub API and parses JSON with jq. This provides a compact summary without navigating to the web interface.

Can I check the status of all open pull requests across my repositories at once?

Yes, you can check the status of all open pull requests across repositories owned by the authenticated user. The script aggregates mergeability, review, and CI status for all open PRs in one readable summary.

Do I need to authenticate with the GitHub CLI to check pull request status?

Yes, authentication for the GitHub CLI tool is required to retrieve real-time pull request data. You must be logged into the gh CLI to query the GitHub API for review and mergeability statuses.

What is the best way to quickly assess if a GitHub pull request is ready to merge?

The best way to assess if a GitHub pull request is ready to merge is using a script that queries the GitHub API for mergeability, review comments, and continuous integration checks, presenting the overall status compactly.

Does checking pull request status require installing jq alongside the GitHub CLI?

Yes, checking pull request status requires installing jq alongside the GitHub CLI. The script depends on jq to parse the JSON responses returned by the GitHub API during real-time data retrieval.

Why use a command line script instead of the GitHub interface for pull request status?

Using a command line script for pull request status saves time by eliminating the need to navigate to each pull request on the web. It provides a compact, readable overview of mergeability and CI status directly from any directory.