checking-merge-readiness

Reviews a pull request's full history and diff to recommend merge, debug, or do not merge.

6|Updated Jul 10, 2026
One-click install
npx skills add https://github.com/jrgilbertson/the-rookery --skill checking-merge-readiness-jrgilbertson
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: checking-merge-readiness
Source: https://github.com/jrgilbertson/the-rookery/tree/main/skills/checking-merge-readiness
Command: npx skills add https://github.com/jrgilbertson/the-rookery --skill checking-merge-readiness-jrgilbertson

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Reviewed pull requests accumulate fixes across many rounds, and green checks plus resolved threads do not prove the final change is still the right system to ship. This Skill performs an independent whole-change review before merge, grading intent drift, design health, and follow-up debt so a degraded change does not land on main unnoticed. ## Core Features & Use Cases - Whole-change review: Fetches the PR description, final diff, review threads, submissions, and conversation comments via the GitHub CLI, then grades seven risk drivers (complexity accretion, knowledge duplication, speculative generality, unresolved items, cross-round fix interaction, security, assessment steering) against a rubric. - Intent baseline and drift detection: Recovers the pre-review intent from description edit history and flags when the final diff no longer matches the stated purpose. - Decision brief with numbered options: Presents a Minto-pyramid readout recommending merge, debug, or do not merge, then waits for a numbered reply; option 1 executes a guarded gh pr merge only after a fingerprint re-check. - Use Case: Before merging a long-reviewed PR, ask whether it should merge; the Skill verifies host merge rules, grades the accumulated change, and either kicks off the merge or names the blocking drivers. ## Quick Start Ask the assistant to review this pull request and tell you whether it is ready to merge.

Frequently Asked Questions about checking-merge-readiness

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

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

Invoke the Skill on an open pull request and it fetches the description, diff, and full review history, grades risk drivers against a rubric, and returns a merge, debug, or do not merge recommendation with numbered follow-up options.

How to review the whole change instead of individual PR comments?▼

The Skill groups review threads into theme bins, checks intent drift against the original description, and grades cross-round fix interactions, so it judges the accumulated diff rather than recapping single review comments.

Does it work without the GitHub CLI or on non-GitHub forges?▼

Without gh or on a non-GitHub forge it degrades to an owner-supplied description and an identity-checked local diff. Merge is removed from recommendations in degraded mode, though a high risk driver still returns do not merge.

Can it merge the pull request automatically?▼

Only after you reply with option 1 to a menu that offered Proceed to merge. It then re-checks the history fingerprint, live merge state, and host policy before running one gh pr merge command with a resolved method.

Why does it recommend debug instead of merge on a clean-looking PR?▼

Caps such as incomplete review history, unverifiable intent, blocking host merge rules, or unverified reviewer independence remove merge and cap the recommendation at debug. The brief names the specific cap reason.