skills.rest
Arry8
Arry8COMMUNITY
Explore all skills by this author →
GitHub

github-pr-ready-check

Assess GitHub pull request readiness using gh CLI data.

1|Updated Mar 30, 2026
Search Tags:#github#review#pr#ci#pull-request#checks#gh-cli
One-click install
npx skills add https://github.com/Arry8/openclaw-edge --skill github-pr-ready-check
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-pr-ready-check
Source: https://github.com/Arry8/openclaw-edge/tree/main/skills/github-pr-ready-check
Command: npx skills add https://github.com/Arry8/openclaw-edge --skill github-pr-ready-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps developers decide whether a PR is ready to merge by summarizing CI status, review blockers, and draft state.

Core Features & Use Cases

  • Pre-merge sanity checks: verifies the PR is not a draft, CI checks pass, and there are no blocking reviews.
  • Blocker summary: collects unresolved review comments and current merge state for quick triage.
  • PR overview extraction: fetches title, author, and mergeStateStatus to inform decision making.

Quick Start

Run the PR readiness check for a given repo and PR number using gh pr view and gh pr checks.

Frequently Asked Questions about github-pr-ready-check

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

FAQPage Schema
How do I check if a GitHub pull request is ready to merge?▼

To check if a GitHub pull request is ready to merge, you can automate a pre-merge readiness assessment to verify the PR is not a draft, CI checks pass, and no blocking reviews remain.

How do I get a summary of blocking review comments and CI status for a PR?▼

Getting a summary of blocking review comments and CI status for a PR requires fetching PR details and merge state to collect unresolved review comments and current CI results for quick triage.

Do I need the gh CLI to automate GitHub PR readiness checks?▼

Yes, you need the gh CLI installed and access to the repository to automate GitHub PR readiness checks, as the process relies on gh pr view and gh pr checks commands to fetch details.

What GitHub PR metadata is needed to assess merge readiness?▼

Assessing merge readiness uses GitHub PR metadata including the draft status, CI check results, blocking review comments, title, author, and mergeStateStatus to inform the final merge decision.

Can I extract the mergeStateStatus of a pull request to decide if it is ready?▼

Yes, you can extract the mergeStateStatus of a pull request alongside the title and author to quickly inform your decision making regarding whether the PR is ready to merge.

Why does my PR readiness check fail even when CI checks pass?▼

A PR readiness check may fail even when CI checks pass if the pull request is still in a draft state or if there are unresolved blocking review comments preventing the merge.

Related Skills

Explore More Software Engineering Skills→
zhouboyu-xrealzhouboyu-xreal

github-auth

Configure HTTPS tokens, SSH keys, and gh CLI authentication for GitHub repositories and APIs.

Community
Intermediate
lucasfcostalucasfcosta
62

pr-monitoring

Monitor a GitHub pull request until merge and required checks pass.

Community
Intermediate
chf3198chf3198

github-review-merge-admin

Validate GitHub pull request approvals, status checks, and merge readiness.

Community
Intermediate
tonykooptonykoop

merge-review

Automate PR review and merge workflows across WRFCoin repositories.

Community
Intermediate