GitHub PR Status

Checks GitHub PR status including CI results, reviews, and merge readiness via API or CLI.

1|1|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/dtsong/claude-code-windows-setup --skill github-pr-status
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: GitHub PR Status
Source: https://github.com/dtsong/claude-code-windows-setup/tree/main/skills/github-workflow/skills/gh-pr-status
Command: npx skills add https://github.com/dtsong/claude-code-windows-setup --skill github-pr-status

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps developers quickly understand the status of a GitHub Pull Request, including its CI/CD pipeline results, review feedback, and overall merge readiness, reducing the time spent manually checking these details.

Core Features & Use Cases

  • Comprehensive Status Check: Gathers information on CI checks, reviews, and merge conflicts.
  • Targeted Information: Allows focusing on specific aspects like checks or reviews.
  • Use Case: Before merging a feature branch, use this Skill to confirm all automated checks have passed and that all required reviewers have approved the changes.

Quick Start

Check the status of the pull request for the current branch.

Frequently Asked Questions about GitHub PR Status

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

FAQPage Schema
How do I check GitHub pull request status including CI checks and reviews?

To check GitHub pull request status, you can fetch CI results, review feedback, and merge readiness using GitHub's API or CLI. This aggregates automated checks and reviewer approvals to confirm a PR is ready to merge.

Can I check merge readiness for a specific GitHub pull request number?

Yes, you can check merge readiness for a specific GitHub pull request number. The status check supports targeting a specific PR or analyzing the current branch, gathering data on CI pipeline results and required reviewer approvals.

What's the best way to monitor GitHub CI status before merging a feature branch?

The best way to monitor GitHub CI status before merging is to run a comprehensive status check that gathers information on automated pipeline results, review feedback, and merge conflicts, reducing time spent manually verifying these details.

Does this PR status check require the GitHub CLI to fetch review and CI data?

No, it does not strictly require the GitHub CLI. The PR status check integrates with GitHub's API or CLI to fetch and analyze pull request data, providing actionable insights on CI results and review status.

Can I focus on just code review status instead of full PR readiness?

Yes, you can focus specifically on code review status. The PR status check provides targeted information options, allowing you to isolate specific aspects like CI checks or reviewer feedback rather than fetching the entire merge readiness report.

Why does my GitHub pull request show as not ready to merge despite passing CI?

A GitHub pull request may show as not ready to merge despite passing CI if required reviewers have not approved the changes or if merge conflicts exist. A comprehensive status check analyzes reviews and conflicts alongside CI results.