skills.rest
VilnaCRM-Org
VilnaCRM-OrgOFFICIAL
Explore all skills by this author →
GitHub

github-pr-merge-readiness-audit

Audits GitHub pull requests for merge readiness across approvals, conflicts, checks, threads, and protection rules.

1|Updated Jun 9, 2026
Search Tags:#code review#pull request#github#audit#merge readiness#branch protection#ci checks
One-click install
npx skills add https://github.com/VilnaCRM-Org/claude-plugins --skill github-pr-merge-readiness-audit-vilnacrm-org
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-pr-merge-readiness-audit
Source: https://github.com/VilnaCRM-Org/claude-plugins/tree/main/plugins/react-frontend-sdlc/skills/github-pr-merge-readiness-audit
Command: npx skills add https://github.com/VilnaCRM-Org/claude-plugins --skill github-pr-merge-readiness-audit-vilnacrm-org

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Green CI checks do not mean a pull request can merge. Approvals may sit on stale commits, reviews may be dismissed by base-branch merges, review threads may be unresolved, and branch protection rules may still block the merge. This Skill audits all five readiness dimensions independently so you know exactly what blocks each PR. ## Core Features & Use Cases - Five-dimension audit: Verifies approvals on the current head SHA, merge conflicts, check statuses (including skipped and cancelled runs), unresolved review threads, and branch protection rules. - Blocker diagnosis with fixes: Maps each blocker — stale approvals, commitlint failures, missing CODEOWNERS reviews, open threads — to the single action that clears it. - Batch triage and merge ordering: Groups multiple PRs by verdict and proposes a merge order, flagging at-risk PRs whose approvals predate a base merge. - Use Case: You have five open PRs that all show green checks but none will merge. Run the audit to learn that two have approvals on stale SHAs, one has an unresolved thread, one is missing a CODEOWNERS review, and only one is actually ready — then land them in the right order. ## Quick Start Audit all open pull requests in this repository and tell me which ones are merge-ready, what blocks the rest, and the order to merge them in.

Frequently Asked Questions about github-pr-merge-readiness-audit

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

FAQPage Schema
Why does my GitHub PR show green checks but still will not merge?▼

Green checks only cover one of five readiness dimensions. The PR may have approvals on a stale head SHA, unresolved review threads, merge conflicts, or unsatisfied branch protection rules such as a required CODEOWNERS review.

How do I check if a PR approval is on the current commit?▼

Compare each reviewer's most recent review commit_id against the PR head SHA and confirm the state is APPROVED. An approval on an older commit still displays as approved in the GitHub UI but does not satisfy merge requirements.

Do AI reviewer approvals satisfy GitHub required-reviewer rules?▼

No. AI reviewer approvals do not satisfy a required-reviewer or CODEOWNERS protection rule. A PR touching an owned path needs the human owner's review requested and granted before it can merge.

Why did merging the base branch dismiss my PR approvals?▼

Merging the base branch into a PR changes the head commit, which auto-dismisses prior approvals under dismissal-on-stale-review settings. Push a real commit and re-request the review; AI reviewers often decline to re-review a pure merge commit.

Is a cancelled CI check run a merge blocker?▼

Not necessarily. A cancelled run followed by a later successful run on the same check is fine — read the latest attempt. Similarly, conditional jobs that legitimately report SKIPPED, such as changed-only e2e specs, are not failures.

When should I not use a merge readiness audit?▼

Do not use it to fix the underlying failures — that is the job of the gate that failed. The audit only diagnoses which of the five dimensions blocks each PR and names the single action that clears it.

Related Skills

Explore More Software Engineering Skills→
pydanticpydantic
19.6k

pushing-commits-to-the-repo

Manages the full pull request lifecycle from opening through CI monitoring and comment triage.

Official
Advanced
gaogg521gaogg521
33

pr-automation

Automate pull request reviews, fixes, CI checks, and merges.

Community
Advanced
shiimanshiiman
2

pr-approve

Automates GitHub pull request approval after verifying CI status and code quality.

Community
Intermediate
shawn-sandyshawn-sandy

merge

Verifies pull request readiness gates and merges approved PRs via GitHub CLI.

Community
Advanced