skills.rest
jason660519
jason660519COMMUNITY
Explore all skills by this author →
GitHub

check-pr

Identify and resolve blockers on open GitHub PRs from CI checks and review comments.

Updated May 11, 2026
Search Tags:#automation#github#review#pr#pull-request#review-threads#verify-baseline
One-click install
npx skills add https://github.com/jason660519/Project-Manager --skill check-pr-jason660519
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: check-pr
Source: https://github.com/jason660519/Project-Manager/tree/main/.agents/skills/check-pr
Command: npx skills add https://github.com/jason660519/Project-Manager --skill check-pr-jason660519

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Open PRs often stall due to unresolved reviewer comments, failing checks, and incomplete PR bodies. This Skill helps identify blockers on an already-open PR, categorize findings, and guide fixes so reviews can be completed efficiently.

Core Features & Use Cases

  • Identify blockers from inline comments, review summaries, and CI checks for open PRs.
  • Wait for pending checks to complete, fetch reviewer input, and compile actionable items.
  • Apply guided fixes and resolve review threads to move PR toward green and merge readiness.

Quick Start

Run the check-pr skill on an open PR to identify blockers and begin resolving review threads.

Frequently Asked Questions about check-pr

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

FAQPage Schema
How do I resolve failing CI checks and reviewer comments on an open GitHub pull request?▼

To resolve open GitHub pull request blockers, run the check-pr task to automatically detect failing CI checks and unresolved reviewer comments. It waits for pending checks to complete, groups findings into actionable items, and guides safe fixes to move the PR toward merge readiness.

What is the best way to automate identifying blockers on a stalled pull request?▼

Automating pull request blocker identification involves scanning inline comments, review summaries, and CI checks to categorize incomplete PR bodies. This process compiles reviewer input and failing checks into actionable items, guiding fixes that pass verify:baseline before merging.

Does check-pr wait for pending GitHub CI checks to complete before reporting blockers?▼

Yes, check-pr waits for pending GitHub CI checks to complete before reporting blockers. It fetches reviewer input after checks finish, ensuring that all failing statuses and inline review comments are compiled into a comprehensive set of actionable items for resolution.

How do I address review threads on a GitHub PR to make it merge ready?▼

To address review threads on a GitHub PR, apply the guided fixes provided for each categorized blocker. This includes resolving inline comments and incomplete PR bodies, ensuring all changes pass verify:baseline checks before the pull request safely reaches merge readiness.

Can I use this to fix incomplete PR bodies and failing checks across PM tooling?▼

Yes, you can use this to fix incomplete PR bodies and failing checks across PM's tooling. It coordinates CI checks, inline comments, and review threads, applying guided fixes that pass verify:baseline to ensure safe merging for open pull requests.

Related Skills

Explore More Software Engineering Skills→
openshiftopenshift
71

investigate-ci-failure

Diagnose CI/Prow failures for GitHub PRs using gh CLI data.

Official
Advanced
ShreeyakShreeyak

pr-review-post

Post draft replies and resolve GitHub PR review threads from a validated plan file.

Community
Advanced
tribedotruntribedotrun
8

mando-pr

Create GitHub pull requests and trigger AI reviewers with CI monitoring.

Official
Advanced
orekyuuorekyuu

get-pr-info

Retrieves GitHub PR titles, descriptions, CI statuses, and comments via CLI/API.

Community
Intermediate