skills.rest
mvillmow
mvillmowCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

verify-pr-ready

Verify GitHub pull requests for CI checks, approvals, and merge conflicts.

18|5|Updated Nov 3, 2025
Search Tags:#workflow#ci/cd#pull request#github#qa#merge readiness#approvals
One-click install
npx skills add https://github.com/mvillmow/ProjectOdyssey --skill verify-pr-ready
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verify-pr-ready
Source: https://github.com/mvillmow/ProjectOdyssey/tree/main/.claude/skills/verify-pr-ready
Command: npx skills add https://github.com/mvillmow/ProjectOdyssey --skill verify-pr-ready

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, jq.

What problem does it solve?

Merging a pull request prematurely without all checks passing can introduce bugs, break the main branch, and lead to costly rollbacks.

Core Features & Use Cases

  • Comprehensive Readiness Check: Verifies that a PR meets all requirements before merging, including CI status, required approvals, and absence of conflicts.
  • Blocking Issue Identification: Clearly identifies what prevents a PR from merging (e.g., failing CI, pending changes, stale branch).
  • Use Case: Before merging a critical pull request, use this skill to perform a final check, ensuring all CI checks are green, approvals are met, and there are no merge conflicts.

Quick Start

Use the verify-pr-ready skill to check the full status of pull request #42, including CI and reviews.

Frequently Asked Questions about verify-pr-ready

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

FAQPage Schema
How do I verify a pull request is ready to merge?▼

Verify PR readiness by checking that CI checks pass, required approvals are satisfied, and no merge conflicts exist. This skill queries GitHub to confirm all conditions are met before merging.

Can I check PR merge readiness without manually reviewing each status?▼

Yes. This skill automates the readiness check by querying CI status, review approvals, mergeable state, and branch protection compliance through GitHub CLI, eliminating manual verification steps.

What blocks a pull request from merging?▼

A PR cannot merge if CI checks are failing, required approvals are pending, merge conflicts exist, or branch protection rules are not satisfied. This skill identifies which specific blocker prevents merging.

Does this work with GitHub branch protection rules?▼

Yes. The skill verifies branch protection compliance by querying GitHub to ensure a PR meets all protection requirements—including status checks and approval rules—before allowing merge.

How do I check multiple pull requests for merge readiness across projects?▼

This skill supports batch merge workflows by querying PR status across multiple projects via GitHub CLI. Run the verification against each PR to identify which are ready and which have blocking issues.

Related Skills

Explore More Software Engineering Skills→
datasurfacedatasurface

Setup Branch Protection

Configure GitHub branch protection with required status checks for DataSurface PR Validator.

Official
Advanced
MFS-codeMFS-code
8

land-and-deploy

Merge a prepared pull request and deploy with canary verification.

Community
Advanced
baphledbaphled
1

github-expert

Automate GitHub PR reviews, CI status checks, and metadata queries via gh CLI.

Community
Intermediate
HomericIntelligenceHomericIntelligence
18

verify-pr-ready

Validate GitHub Pull Requests for CI status, approvals, and merge conflicts.

Official
Intermediate