verify-pr-ready
Verify a PR is ready for merge (CI passing, approvals, no conflicts). Use before merging to ensure all requirements met.
When & Why to Use This Skill
This Claude skill automates the verification of GitHub Pull Requests by checking CI status, reviewer approvals, and merge conflicts. It ensures that all branch protection rules and quality requirements are met before merging, streamlining the software delivery lifecycle and preventing integration errors.
Use Cases
- Pre-merge Validation: Automatically verify that a PR is fully compliant with CI/CD requirements and team policies before manual or automated merging.
- Continuous Integration Monitoring: Check the real-time status of CI pipelines and test results to identify blocking issues early in the review process.
- Branch Protection Compliance: Ensure that all mandatory reviews and status checks are satisfied according to repository settings to maintain code quality.
- Automated Release Workflows: Use as a gatekeeper in automated deployment scripts to confirm PR readiness before triggering production releases.
| name | verify-pr-ready |
|---|---|
| description | "Verify a PR is ready for merge (CI passing, approvals, no conflicts). Use before merging to ensure all requirements met." |
| category | github |
Verify PR Ready for Merge
Check that PR meets all requirements before merging.
When to Use
- Before merging a PR manually
- Checking if PR is ready for automated merge
- Validating PR readiness in batch merge operations
- Before requesting final approval
- Verifying branch protection rule compliance
Quick Reference
# Check PR status
gh pr view <pr>
# Check CI status
gh pr checks <pr>
# View PR review status
gh pr view <pr> --json reviews
# Check for conflicts
gh pr status <pr> | grep -i "conflict"
# Get PR details as JSON
gh api repos/OWNER/REPO/pulls/<pr> --jq '.{mergeable, merged, title}'
Readiness Checklist
Before merging, verify:
- All CI checks passing (no failures or pending)
- Required number of approvals received
- No requested changes from reviewers
- PR is linked to issue
- No merge conflicts detected
- Branch is up to date with main
- All branch protection rules satisfied
- Code review completed
Workflow
- View PR: Get full PR details with
gh pr view <pr> - Check CI: Verify all checks passing with
gh pr checks <pr> - Check reviews: Confirm approvals with
gh pr view --json reviews - Check conflicts: Test mergeability (mergeable field)
- Verify rules: Check branch protection satisfaction
- Final validation: Confirm all requirements met
- Report status: Merge or identify blocking issues
Blocking Issues
PR cannot merge if:
- CI checks failing (pipeline errors or test failures)
- Merge conflicts exist (requires manual resolution)
- Required approvals not met (check branch protection rules)
- Requested changes pending (from required reviewers)
- Branch is stale (needs rebase on main)
- Protected rule violations (size, format, etc.)
Output Format
Report readiness status with:
- Overall Status - Ready or Not Ready with reasons
- CI Status - All checks + counts of passing/failing
- Review Status - Approvals count and any requested changes
- Merge Status - Mergeable true/false and conflict info
- Blocking Issues - List of what prevents merge (if any)
- Recommendation - Approve for merge or required actions
Error Handling
| Problem | Solution |
|---|---|
| Mergeable check fails | Rebase on main and resolve conflicts |
| CI pending | Wait for checks to complete |
| Approvals missing | Request review from required reviewers |
| Auth error | Check gh auth status permissions |
| PR not found | Verify PR number exists |
References
- See gh-review-pr for comprehensive review checklist
- See gh-batch-merge-by-labels for batch merge workflow
- See CLAUDE.md for PR linking and branch protection rules